On Tue, Aug 15 2017, Robert Ewald wrote: > The location of the shell is not always /bin/sh. Use the > shell-file-name variable to be able to specify the shell location. > --- > emacs/notmuch-lib.el | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/emacs/notmuch-lib.el b/emacs/notmuch-lib.el > index 337b20ac..8dffe9f2 100644 > --- a/emacs/notmuch-lib.el > +++ b/emacs/notmuch-lib.el > @@ -921,7 +921,7 @@ status." > (command (or (executable-find notmuch-command) > (error "command not found: %s" notmuch-command))) > (proc (apply #'start-process name buffer > - "/bin/sh" "-c" > + shell-file-name "-c" > "exec 2>\"$1\"; shift; exec \"$0\" \"$@\"" > command err-file args))) > (process-put proc 'err-file err-file) I don't yet know a (unix) system where /bin/sh did not provide a bourne compatible shell that supports the syntax used above. My shell-file-name expands to "/bin/zsh". I wonder if it expanded like "/usr/bin/tcsh" or "/path/to/fish" or "/path/to/rc" those worked here. Tomi > -- > 2.11.0 _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch