Re: xargs --negate-interactive

2016-07-18 Thread Bernhard Voelker
On 07/18/2016 01:45 PM, James Youngman wrote: > On Mon, Jul 18, 2016 at 6:52 AM, Bernhard Voelker > wrote: >> a) --interactive=default-novs. --interactive=default-yes > I have a preference for (a) [...] Great, let's do it that way, thanks! Have a nice day, Berny

Re: xargs --negate-interactive

2016-07-18 Thread 積丹尼 Dan Jacobson
Thank you all for working on my idea. As I am kind of busy, I will leave it all up to you to perfect it.

Re: xargs --negate-interactive

2016-07-18 Thread James Youngman
I have a preference for (a) because I'm mildly philosophically opposed to the abbreviation option (among other reasons, because supporting the shortest unique abbreviation gives rise to surprising results when other possible expansions appear in later releases). On Mon, Jul 18, 2016 at 6:52 AM, Be

Re: xargs --negate-interactive

2016-07-17 Thread Bernhard Voelker
On 07/17/2016 08:49 PM, James Youngman wrote: > I can see your point, but I think it might seem surprising for > --interactive=no to turn on the interactive behaviour. Can we refine > your proposal so it isn't surprising in this way, somehow? Ah, that was ambigous, too, I must admit. Maybe one

Re: xargs --negate-interactive

2016-07-17 Thread James Youngman
I can see your point, but I think it might seem surprising for --interactive=no to turn on the interactive behaviour. Can we refine your proposal so it isn't surprising in this way, somehow?

Re: xargs --negate-interactive

2016-07-17 Thread Bernhard Voelker
On 07/16/2016 04:17 PM, James Youngman wrote: > I quite like the idea. Here's an example implementation of a flag that > could be used in a shell function/alias, if that's your thing. Comments? > > 0001-xargs-add-new-option-interactive-default-yes-modifyi.patch > > > From bfea9c150229db14316

Re: xargs --negate-interactive

2016-07-16 Thread James Youngman
I quite like the idea. Here's an example implementation of a flag that could be used in a shell function/alias, if that's your thing. Comments? On Sun, Apr 17, 2016 at 9:12 PM, Bernhard Voelker wrote: > On 04/10/2016 04:26 PM, 積丹尼 Dan Jacobson wrote: > >> "BV" == Bernhard Voelker writes:

Re: xargs --negate-interactive

2016-04-17 Thread Bernhard Voelker
On 04/10/2016 04:26 PM, 積丹尼 Dan Jacobson wrote: >> "BV" == Bernhard Voelker writes: > BV> Well, there are many possibilities, but there is already a way to > BV> to do it in xargs. So what would you want to achieve by saving a RET? > BV> I don't think it's about the wearing of the ENTER key o

Re: xargs --negate-interactive

2016-04-10 Thread 積丹尼 Dan Jacobson
> "BV" == Bernhard Voelker writes: BV> Well, there are many possibilities, but there is already a way to BV> to do it in xargs. So what would you want to achieve by saving a RET? BV> I don't think it's about the wearing of the ENTER key on your keyboard? Thank you. If there is a way to do $

Re: xargs --negate-interactive

2016-04-10 Thread Bernhard Voelker
On 04/10/2016 03:52 PM, 積丹尼 Dan Jacobson wrote: > BV> Without RET, this would all be mangled and the commands would be > BV> unreadable on a terminal. > > All I know is there could be an additional option added to switch it > into a mutt mail reader like mode just before waiting for each response,

Re: xargs --negate-interactive

2016-04-10 Thread 積丹尼 Dan Jacobson
BV> Without RET, this would all be mangled and the commands would be BV> unreadable on a terminal. All I know is there could be an additional option added to switch it into a mutt mail reader like mode just before waiting for each response, wherein one character is read without waiting for a RET.

Re: xargs --negate-interactive

2016-04-10 Thread Bernhard Voelker
On 04/10/2016 03:12 PM, 積丹尼 Dan Jacobson wrote: > Wait, how about an option to eliminate the need for RET: > > so now all they would need to type is > > RET y RET RET y y > or even > x y x x y y > or any non y ... > wait, how about just n,y,and q(to quit), and maybe "." to d

Re: xargs --negate-interactive

2016-04-10 Thread 積丹尼 Dan Jacobson
> "BV" == Bernhard Voelker writes: BV> Although you're maybe right from the logical point of view, I'm not BV> sure if 'xargs -p' is used often enough to warrant adding such an option BV> to the code. The next user may then come and want to have yet another BV> option like --interactive-assu

Re: xargs --negate-interactive

2016-04-10 Thread Bernhard Voelker
On 04/08/2016 03:52 PM, 積丹尼 Dan Jacobson wrote: > xargs has > >-p, --interactive > Prompt the user about whether to run each command line and read > a line from the terminal. Only run the command line if the re- > sponse starts with `y' or `Y'.

xargs --negate-interactive

2016-04-08 Thread 積丹尼 Dan Jacobson
xargs has -p, --interactive Prompt the user about whether to run each command line and read a line from the terminal. Only run the command line if the re- sponse starts with `y' or `Y'. Implies -t. But then one needs to enter y RET y RET y RET