unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Joel Ray Holveck <joelh@piquan.org>
Cc: 23914@debbugs.gnu.org
Subject: bug#23914: 24.5; tramp-get-remote-path fails with some shells if tramp-own-remote-path is used
Date: Sat, 09 Jul 2016 13:38:28 +0200	[thread overview]
Message-ID: <8737njt51n.fsf@gmx.de> (raw)
In-Reply-To: <87bn28a4nb.fsf@thor.piquan.org> (Joel Ray Holveck's message of "Fri, 08 Jul 2016 01:57:28 -0700")

Joel Ray Holveck <joelh@piquan.org> writes:

Hi Joel,

> On FreeBSD, if tramp-own-remote-path is a member of, then using tramp's
> sudo method raises an error similar to:
>
>     byte-code: `/bin/sh -l -c 'echo 9905dea968fdd4a549d307a722e8109b \"$PATH\"'' returns with error

Well, meanwhile Tramp doesn't raise an error anymore. It simply ignores
it, what's not a solution, I know.

> On FreeBSD, /bin/sh does not accept the -l flag.  bash, dash, and ksh
> do, but that's not part of the POSIX shell requirements (see
> http://pubs.opengroup.org/onlinepubs/009695399/utilities/sh.html), and
> historically the Bourne shell doesn't.

Unfortunately, Posix does not specify how to force a login shell,
evaluating its ~/.profile and friends. If somebody knows a portable way,
how one could determine the $PATH settings of a login shell, I'll add it
to Tramp happily.

Best regards, Michael.





  reply	other threads:[~2016-07-09 11:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08  8:57 bug#23914: 24.5; tramp-get-remote-path fails with some shells if tramp-own-remote-path is used Joel Ray Holveck
2016-07-09 11:38 ` Michael Albinus [this message]
2016-07-09 12:23   ` Andreas Schwab
2016-07-10 15:07     ` Michael Albinus
2016-08-20 10:05       ` Michael Albinus
2016-08-28  8:20         ` 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=8737njt51n.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=23914@debbugs.gnu.org \
    --cc=joelh@piquan.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://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).