#3532: Use $SHELL when running mailcap-related commands
-------------------------+--------------------------------------------------
Reporter: vinc17 | Owner: mutt-dev
Type: enhancement | Status: new
Priority: major | Milestone:
Component: mutt | Version:
Keywords: |
-------------------------+--------------------------------------------------
Comment(by vinc17):
There is other software that uses $SHELL for commands (possibly including
in system-wide configuration). If you set $SHELL to a shell sufficiently
incompatible with POSIX, you may already have problems. Also note that
Debian's /etc/mailcap uses underspecified and obsolescent POSIX features
(it probably works with both bash and dash, but the system could have
another shell for /bin/sh, which is just a symlink...).
Now, an alternative could be that the shell be specified as a Mutt
variable (/bin/sh by default). That could be a replacement for the
compile-time EXECSHELL. Indeed /bin/sh may change between Mutt builds, so
that it can be better to have it set at run time.
Or any other alternative that would allow to have /bin/sh run in a
corrected environment.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3532#comment:10>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
