From: Robert Ewald <robewald@gmx.net>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: Make the shell location configurable
Date: Wed, 16 Aug 2017 09:17:18 +0200 [thread overview]
Message-ID: <57061C6E-AF81-4C8B-9BA8-62747BB1806D@gmx.net> (raw)
In-Reply-To: <874lt8jtak.fsf@tethera.net>
> On 16 Aug 2017, at 01:38, David Bremner <david@tethera.net> wrote:
>
> Robert Ewald <robewald@gmx.net> writes:
>
>> 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.
>
> Yeah, I was sloppy. Hopefully POSIX compatibility is enough (if not we
> can probably fix that). But as you note there's no guarantee
> shell-file-name is POSIX compatible.
>
> d
I did some research: apparently shell-file-name should be POSIX compatible,
otherwise many plugins don't work. explicit-shell-file-name however can be set to
fish or tcsh if you want to use that in M-x shell.
https://emacs.stackexchange.com/questions/28647/how-do-i-change-the-default-shell-for-shell-command
So I think the patch as submitted is good, please apply.
Thanks.
Robert.
next prev parent reply other threads:[~2017-08-16 7:17 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
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 [this message]
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=57061C6E-AF81-4C8B-9BA8-62747BB1806D@gmx.net \
--to=robewald@gmx.net \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/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).