Re: execlineb -S does not stop the command from running

2018-07-29 Thread Joshua Haase
Jesse Young (2018-07-29 12:19): |> >$ execlineb -S1 -c 'echo wrong' |> >execlineb: warning: too few arguments: expecting at least 1 but got 0 |> >wrong |> >``` |> |> It's not an error, it's actually a bugfix. As you can see, the message |> is a "warning", not a "fatal", which means it does not

Re: execlineb -S does not stop the command from running

2018-07-29 Thread Jesse Young
On Sun, Jul 29, 2018, at 08:50, Laurent Bercot wrote: > >`execline` does indeed exits when not given arguments, and displays the > >error `execlineb: warning: too few arguments: expecting at least 1 but > >got 0` but the first command gets run. > > > >``` > >$ execlineb -S1 -c 'echo wrong' >

Re: execlineb -S does not stop the command from running

2018-07-29 Thread Laurent Bercot
`execline` does indeed exits when not given arguments, and displays the error `execlineb: warning: too few arguments: expecting at least 1 but got 0` but the first command gets run. ``` $ execlineb -S1 -c 'echo wrong' execlineb: warning: too few arguments: expecting at least 1 but got 0 wrong