Stephane CHAZELAS <stephane.chaze...@gmail.com> wrote:
> Let's face it, a shell that would leave the "m" option "on" when
> the user explicitly requested it to be "off" in
>
> sh +m
>
> is a bug (and in this case also a conformance bug for shells
> that support UP though it may need to be clarified).
Since POSIX requires that an interactive shell should automatically turn on -m
but does not mention _when_ this decision should be made, a shell that _finally_
has -m turned on behaves correct. This is since it first turned -m off as a
result from calling "sh +m", then checked whether it is interactive and as a
result followed the POSIX requirement to turn on -m.
ksh88, ksh93, bash, bosh end up with -m turned on in this case.
Jörg
--
EMail:jo...@schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
