Hello, Thanks for reviewing the patch. > On 15 Aug 2017, at 18:02, David Bremner <david@tethera.net> wrote: > > Robert Ewald <robewald@gmx.net> writes: > >> The location of the shell is not always /bin/sh. Use the >> shell-file-name variable to be able to specify the shell location. >> --- > > Can you say a bit more about the problem you are trying to solve? I > think shell-file-name is not guaranteed to be Bourne shell compatible. I would like to use notmuch with a remote-notmuch script on emacs on windows (not cygwin). Right now I cannot make this work, because that version of emacs doesn't have any kind of unix style paths. I have an installation of msys that provides the usual unix tools. This is configured in the init.el by setting shell-file-name. Does the shell-file-name have to be bourne shell compatible? My understanding is that using "/bin/sh" requires a POSIX compatible shell, bash specific shell scripts should be invoked with e.g. /bin/bash. I believe a POSIX compatible shell is sufficient in this particular case. Of course, if shell-file-name is not POSIX compatible this line may not work. Another way would be to introduce another configuration variable, but I would like to avoid that. Best regards Robert _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch