From: Tomi Ollila <tomi.ollila@iki.fi>
To: Robert Ewald <robewald@gmx.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: Make the shell location configurable
Date: Tue, 15 Aug 2017 16:53:50 +0300 [thread overview]
Message-ID: <m2lgmlndht.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <20170814223623.28411-1-robewald@gmx.net>
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
next prev parent reply other threads:[~2017-08-15 13:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 22:36 [PATCH] emacs: Make the shell location configurable Robert Ewald
2017-08-15 13:53 ` Tomi Ollila [this message]
2017-08-15 16:02 ` David Bremner
2017-08-15 20:04 ` Robert Ewald
2017-08-15 23:38 ` David Bremner
2017-08-16 7:17 ` Robert Ewald
2017-08-16 11:09 ` David Bremner
2017-08-16 20:16 ` Robert Ewald
2017-08-17 11:44 ` David Bremner
2017-08-17 12:15 ` Tomi Ollila
2017-08-17 21:46 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2lgmlndht.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=notmuch@notmuchmail.org \
--cc=robewald@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).