From: Michael Albinus <michael.albinus@gmx.de>
To: "Jürgen A. Erhard" <jae@jaerhard.com>
Cc: 24338@debbugs.gnu.org
Subject: bug#24338: 24.5; compile-start has /bin/sh hardcoded for remote executions.
Date: Tue, 30 Aug 2016 17:42:34 +0200 [thread overview]
Message-ID: <87a8fu1cwl.fsf@gmx.de> (raw)
In-Reply-To: <871t164nxu.fsf@debian32vm.home.jaerhard.com> ("Jürgen A. Erhard"'s message of "Tue, 30 Aug 2016 11:15:57 +0200")
Jürgen A. Erhard <jae@jaerhard.com> writes:
> Title says all, it checks with file-remote-p and the hardcodes /bin/sh.
> It should ideally check the login shell of the remote system or... but
> that all needs knowledge it's not supposed to have, I guess. Hmm, but
> file-remote-p does use a handler system. So... have to ponder (if it's
> not completely changed in 25)
>
> At least document it, and please give a way to override in the "Use
> shell-file-name, I know what I'm doing".
`shell-file-name' is often wrong for remote systems; there could be
another OS, for example. "/bin/sh" is POSIX and can be assumed to exist.
How shall one know the remote login shell in advance?
And, in order to find a proper solution, maybe you could show a use case
where "/bin/sh" is simply wrong?
Best regards, Michael.
next prev parent reply other threads:[~2016-08-30 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 9:15 bug#24338: 24.5; compile-start has /bin/sh hardcoded for remote executions Jürgen A. Erhard
2016-08-30 15:42 ` Michael Albinus [this message]
2016-08-30 15:55 ` Andreas Schwab
2016-08-30 16:02 ` Michael Albinus
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8fu1cwl.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=24338@debbugs.gnu.org \
--cc=jae@jaerhard.com \
/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://git.savannah.gnu.org/cgit/emacs.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).