-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
org-web-tools-archive-view has a problem with "--auto-compress" #70
Comments
Hi, Sorry, I don't understand: IIUC the solution in the linked issue is to install and use the GNU version of tar, which should make this Elisp advice unnecessary. |
Hi! |
Did you follow the suggestions in #65 (comment) and compare with the following comment? It sounds like you still have Emacs using the non-GNU version of tar, as he did until he did some further configuration. |
Yes I did all the steps in the issue. I put this into my typeset -U path
# PREpend the gnu utils paths
for bindir in "$(brew --prefix)/opt/"*"/libexec/gnubin"; do path=($bindir ${path[@]}); done
# APPend the other homebrew bins
for bindir in "$(brew --prefix)/opt/"*"/bin"; do path+=($bindir); done
# prepend the gnu man pages (optional)
for mandir in "$(brew --prefix)/opt/"*"/libexec/gnuman"; do manpath=($mandir ${manpath[@]}); done
# append the other homebrew man pages (optional)
for mandir in "$(brew --prefix)/opt/"*"/share/man/man1"; do manpath+=($mandir); done
export PATH path and even I tried the linuxify solution and nothing worked for me. |
One final check: after doing that, did you log out and back in again? |
You should probably use the exec-path-from-shell package for Emacs when running on macOS, in order to properly set the shell path. I suggest running this in your init.el file. (use-package exec-path-from-shell
:ensure t
:config
(when (memq window-system '(mac ns x))
(exec-path-from-shell-initialize))) |
In macOS I had the very same issue as #65, with
org-web-tools-archive-view
. Every time I use the function, this message appears,I could solve the problem by removing the
--auto-compress
flag and advising the new function instead of the original one.Maybe this could be applied upstream if you find useful.
Best.
The text was updated successfully, but these errors were encountered: