Re: propagating environment variable via internal command

2018-06-20 Thread Tomas Janousek
Hi Chet and Tomáš, On Wed, Jun 20, 2018 at 10:42:07AM -0400, Chet Ramey wrote: > On 6/20/18 9:25 AM, Tomáš Čech wrote: > >  $ /bin/sh > >  sh-4.4$ VARIABLE=value set -o noglob > >  sh-4.4$ env | grep VARIABLE > >  VARIABLE=value > >  sh-4.4$ > > Posix requires this behavior, which dates back to t

Re: propagating environment variable via internal command

2018-06-20 Thread Chet Ramey
On 6/20/18 9:25 AM, Tomáš Čech wrote: > Hi, > > > when comparing strange behaviors of different shell implementations Tomas > Janousek found this bug > > When using BASH as sh shell... > >  $ ls -l /bin/sh >  lrwxrwxrwx 1 root root 4 Jun 13 16:25 /bin/sh -> bash > > ...internal shell command `

propagating environment variable via internal command

2018-06-20 Thread Tomáš Čech
Hi, when comparing strange behaviors of different shell implementations Tomas Janousek found this bug When using BASH as sh shell... $ ls -l /bin/sh lrwxrwxrwx 1 root root 4 Jun 13 16:25 /bin/sh -> bash ...internal shell command `set' propagates environment variable to the process its run