From: Michael Albinus <michael.albinus@gmx.de>
To: "Matz\, Daniel A. \(JSC-EG511\)" <daniel.a.matz@nasa.gov>
Cc: 29723@debbugs.gnu.org, 24338@debbugs.gnu.org
Subject: bug#24338: bug#29723: 25.3; `compile' doesn't honor `tramp-methods', always uses "/bin/sh"
Date: Sat, 09 Mar 2019 18:10:30 +0100 [thread overview]
Message-ID: <877ed80y9l.fsf@gmx.de> (raw)
In-Reply-To: <87tvu9fguu.fsf@gmx.de> (Michael Albinus's message of "Thu, 22 Feb 2018 11:39:37 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Daniel,
>> Starting with emacs -Q, execute the following:
>>
>> (require 'tramp)
>> (let ((scpx-method (cdr (assoc "scpx" tramp-methods))))
>> (add-to-list 'scpx-method '(tramp-remote-shell "/bin/bash"))
>> (add-to-list 'tramp-methods (cons "scpx" scpx-method)))
>>
>> Then use the "scpx" connection type to find a file on a remote host.
>> Then, use `shell-command' to run "echo $_". I get an output of
>> "/bin/bash". Then, run the same command with `compile'. I get an
>> output of "/bin/sh". I was expecting to again get "/bin/bash".
>
> This is the same problem as bug#24338, I will mark your report as
> duplicate.
>
> In fact, "/bin/sh" is hardcoded for remote compilation in function
> `compilation-start'. This shall be changed, using connection-local
> variables, see (info "(elisp) Connection Local Variables")
>
> It is on my todo list, but less prioritized. I would be happy if
> somebody else takes the ball, and implements this in `compilation-start'.
Finally, I've adapted connection-local variables accordingly, pushed to
the master branch. See the discussion in (info "(emacs) Connection Variables")
>> Thank you!
>>
>> Daniel
Best regards, Michael.
next prev parent reply other threads:[~2019-03-09 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 19:56 bug#29723: 25.3; `compile' doesn't honor `tramp-methods', always uses "/bin/sh" Matz, Daniel A. (JSC-EG511)
[not found] ` <handler.29723.B.151336781326088.ack@debbugs.gnu.org>
2018-02-21 22:13 ` bug#29723: Acknowledgement (25.3; `compile' doesn't honor `tramp-methods', always uses "/bin/sh") Matz, Daniel A. (JSC-EG511)
2018-02-22 6:22 ` Eli Zaretskii
2018-02-22 9:03 ` Michael Albinus
2018-02-22 10:39 ` bug#29723: 25.3; `compile' doesn't honor `tramp-methods', always uses "/bin/sh" Michael Albinus
[not found] ` <87lgflfcdg.fsf@gmail.com>
2018-02-22 12:53 ` Michael Albinus
2019-03-09 17:10 ` Michael Albinus [this message]
2019-03-17 14:09 ` bug#24338: " 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=877ed80y9l.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=24338@debbugs.gnu.org \
--cc=29723@debbugs.gnu.org \
--cc=daniel.a.matz@nasa.gov \
/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).