They say that to help people choose (for example) -I for greater
portability to other systems. Using xargs -i in a script would
perhaps make that script not work on other systems. So we try to
help people choose the more portable options.
If you disagree with the wording, please send a patch p
On 7/29/19 8:52 AM, Bernhard Voelker wrote:
> Thanks, attached as patch with a test case, NEWS entry, etc.
Pushed at:
https://git.sv.gnu.org/cgit/findutils.git/commit/?id=eeefd1dc7
Have a nice day,
Berny
Well the man page and INFO page say depreciated. So better clean them up.
On 7/29/19 1:49 PM, 積丹尼 Dan Jacobson wrote:
> P.S.,
> $ xargs --help
> -I R same as --replace=R
> -i, --replace[=R]replace R in INITIAL-ARGS with names read
> from standard input; if R is unspecified,
>
P.S.,
$ xargs --help
-I R same as --replace=R
-i, --replace[=R]replace R in INITIAL-ARGS with names read
from standard input; if R is unspecified,
assume {}
...
Don't you want to mention one i
Well all I know is the whole idea of xargs is to *separate* the things
coming in into separate arguments.
So when the user uses -I, he expects it to just act the same, with the
extra feature being that he can now also put things into the beginning
or middle of lines, not just the ends.
Never in h
On 7/25/19 6:28 PM, 積丹尼 Dan Jacobson wrote:
> "Warning: whatever you feed in will become one argument glued together."
IMO that doesn't sound too far away from what is currently in the manpage:
"[...]
Also, unquoted blanks do not terminate input items;
instead the separator is the newlin
On 7/24/19 11:28 PM, Eric Blake wrote:
> Looks reasonable to me (other than line wrapping).
Thanks, attached as patch with a test case, NEWS entry, etc.
Comments?
Have a nice day,
Berny
From eeefd1dc72102c5d8c70912be943a71a0fb153aa Mon Sep 17 00:00:00 2001
From: Bernhard Voelker
Date: Sun, 28 Ju
JY> Please feel that you should phrase your suggestion in the form of a patch.
I don't know what to write.
"Warning: whatever you feed in will become one argument glued together."
On Thu, Jul 25, 2019 at 3:28 PM 積丹尼 Dan Jacobson wrote:
> still needs to add a tip to use -p or -t to see the quoting realities of
> how REPLACE-STR is used...
Please feel that you should phrase your suggestion in the form of a patch.
OK, but
'-I REPLACE-STR'
'--replace[=REPLACE-STR]'
'-i[REPLACE-STR]'
Replace occurrences of REPLACE-STR in the initial arguments with
names read from standard input. Also, unquoted blanks do not
terminate arguments; instead, the input is split at newlines on
On 7/24/19 4:20 PM, Bernhard Voelker wrote:
> I agree that another new option is way too much. That question to the user
> is meant for interactive use only anyway, so what about simply:
>
> diff --git a/xargs/xargs.c b/xargs/xargs.c
> index 913328b8..85084123 100644
> --- a/xargs/xargs.c
> +++
On 7/24/19 4:30 PM, Eric Blake wrote:
> On 7/24/19 6:28 AM, James Youngman wrote:
>> On Tue, Jul 23, 2019 at 7:51 PM 積丹尼 Dan Jacobson wrote:
>>>
>>> OK.
>>> But I now "demand" that xargs add a --show-quoting or whatever argument,
>>
>> Your demand must be presented in the form of a patch.
>
> Is
On 7/24/19 6:28 AM, James Youngman wrote:
> On Tue, Jul 23, 2019 at 7:51 PM 積丹尼 Dan Jacobson wrote:
>>
>> OK.
>> But I now "demand" that xargs add a --show-quoting or whatever argument,
>
> Your demand must be presented in the form of a patch.
Is a new option necessary, or can we just use gnulib
On Tue, Jul 23, 2019 at 7:51 PM 積丹尼 Dan Jacobson wrote:
>
> OK.
> But I now "demand" that xargs add a --show-quoting or whatever argument,
Your demand must be presented in the form of a patch.
> so that --verbose, and -p, will now show
> 'xdotool' 'mousemove' '0 0' 'click' '1' 'mousemove' 'rest
Plus I'm not sure that
'-I REPLACE-STR'
'--replace[=REPLACE-STR]'
'-i[REPLACE-STR]'
Replace occurrences of REPLACE-STR in the initial arguments with
names read from standard input. Also, unquoted blanks do not
terminate arguments; instead, the input is
OK.
But I now "demand" that xargs add a --show-quoting or whatever argument,
so that --verbose, and -p, will now show
'xdotool' 'mousemove' '0 0' 'click' '1' 'mousemove' 'restore' ?...
vs.
'xdotool' 'mousemove' '0' '0' 'click' '1' 'mousemove' 'restore' ?...
for people who care about those details,
On 7/23/19 1:31 PM, Assaf Gordon wrote:
>
> This is not about "-p", but simply that "{}" puts the entire input line
> ("0 0") as a single parameter (as if quoted).
>
> The correct comparison is:
>
> echo | xargs -p xdotool mousemove 0 0 click 1 mousemove restore
> vs
> echo | xargs -p xdoto
Hello,
On 2019-07-23 9:59 a.m., 積丹尼 Dan Jacobson wrote:
Proof that xargs prompts with the same string, but executes differently:
$ echo 0 0 | xargs -p -I{} xdotool mousemove {} click 1 mousemove restore
xdotool mousemove 0 0 click 1 mousemove restore ?...y
xdotool: Unknown command: 1
Run
Proof that xargs prompts with the same string, but executes differently:
$ echo 0 0 | xargs -p -I{} xdotool mousemove {} click 1 mousemove restore
xdotool mousemove 0 0 click 1 mousemove restore ?...y
xdotool: Unknown command: 1
Run 'xdotool help' if you want a command list
$ echo
20 matches
Mail list logo
