|
From: | Paul Eggert |
Subject: | Re: [PATCH] Add shell-quasiquote. |
Date: | Thu, 22 Oct 2015 08:41:19 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 |
On 10/22/2015 08:03 AM, Eli Zaretskii wrote:
I beg to differ: IMHO, on Unix-like systems, there's no point for >`shell-command' and friends to support anything but /bin/sh, which is >certainly a Bourne shell and hopefully reasonably POSIX compliant.I see your point. However, this is contrary to a very old and documented behavior. Would such a change be acceptable?
I suppose it would be an incompatible change, but I think it'd be a good idea. Emacs already distinguishes between interactive shells and shells invoked as utilities, and uses explicit-shell-file-name for the former but shell-file-name for the latter. We could put into the documentation that the latter should be a POSIX-syntax shell (not "POSIX-conforming" because strict POSIX conformance is relatively rare). People writing Elisp code shouldn't have to worry about the syntax of the C shell, or of some MS-Windows shell.
[Prev in Thread] | Current Thread | [Next in Thread] |