bugzilla-daemon at bugzilla.mindrot.org
2017-Jun-27 02:22 UTC
[Bug 1494] doesn't look on path for $SHELL
https://bugzilla.mindrot.org/show_bug.cgi?id=1494 --- Comment #7 from Vincent Lefevre <vincent-openssh at vinc17.net> --- (In reply to Damien Miller from comment #2)> My copy of Single Unix Specification states: > > > SHELL > > This variable shall represent a pathname of the user's > > preferred command language interpreter. [...] > > Its definition of "pathname": > > > A character string that is used to identify a file. > > [...] > > Note: > > Pathname Resolution is defined in detail in _Pathname Resolution_. > > I'd say that a non-absolute pathname for $SHELL clearly does not > "identify a file" unless one happens to be in the same directory as > the shell itself and the "Pathname Resolution" section doesn't > specify that pathnames be resolved using $PATH.There would be the same issue with $EDITOR, while POSIX also says "pathname" for EDITOR and gives an example with EDITOR=vi (i.e. not an absolute pathname). According to a mail in the Austin Group mailing-list, the valid values for $SHELL should be documented by the platform. For Debian, I've reported: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866060 (bug against the manpages package, which provides the environ(7) man page). -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug.
Maybe Matching Threads
- [Bug 1494] New: doesn't look on path for $SHELL
- [Bug 1762] Improve the documentation w.r.t. "the user's shell"
- Bug#305932: rsync on a directory transfers the files of this directory
- [Bug 1265] SCP progress doesn't map to standard out or standard error
- [Bug 1762] New: Improve the documentation w.r.t. "the user's shell"