Re: Little correction on fdmove doc

2018-07-29 Thread Laurent Bercot
I've found the command intuitive but the documentation confused me a little bit. So here's a patch. ISTR you actually submitted the same thing a few months ago and I did not react. Sorry, I should have replied sooner. The documentation is correct and I won't apply the patch. But it's not

Little correction on fdmove doc

2018-07-29 Thread Joshua Haase
I've found the command intuitive but the documentation confused me a little bit. So here's a patch. >From bb4dbf267857737ad88240d2ad9cead9b3c3481f Mon Sep 17 00:00:00 2001 From: Joshua Haase Date: Sun, 29 Jul 2018 04:44:57 -0500 Subject: [PATCH] fdmove documentation have fd backwards. ---

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

execlineb -S does not stop the command from running

2018-07-29 Thread Joshua Haase
Hi there, First of all, thanks for this fine and useful software on skaware. I'm using execline v2.5.0.0 (and 7ce423). I've tried to use the -S1 option to stop the command from running when not given any arguments. `execline` does indeed exits when not given arguments, and displays the error

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' >