Bug 147595 - xargs -I option does not work
Summary: xargs -I option does not work
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: findutils
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Miloslav Trmač
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-02-09 17:04 UTC by Dag Wieers
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-01-11 14:13:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dag Wieers 2005-02-09 17:04:11 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041020 Galeon/1.3.19

Description of problem:
This is supposed to work, both according to the manual and the
command-line help.

[root@emyn ~]# echo -e "file1\nfile2\nfile3" | xargs -I '**' echo '**'
blah
xargs: invalid option -- I
Usage: xargs [-0prtx] [-E eof-str] [-e[eof-str]] [-I replace-str]
       [-i[replace-str]] [-L max-lines] [-l[max-lines]] [-n max-args]
       [-s max-chars] [-P max-procs] [--null] [--eof[=eof-str]]
       [--replace[=replace-str]] [--max-lines[=max-lines]] [--interactive]
       [--max-chars=max-chars] [--verbose] [--exit]
[--max-procs=max-procs]
       [--max-args=max-args] [--no-run-if-empty] [--version] [--help]
       [command [initial-arguments]]

Report bugs to <bug-findutils>.



Version-Release number of selected component (if applicable):
findutils-4.1.20-7

How reproducible:
Always

Steps to Reproduce:
1. See report
2.
3.
    

Expected Results:  I expect the same result as:

[root@emyn ~]# echo -e "file1\nfile2\nfile3" | xargs -i'**' echo '**' blah
file1 blah
file2 blah
file3 blah


Additional info:

Comment 1 Tim Waugh 2005-02-09 17:07:48 UTC
This will be fixed in 4.2.x, which will be in rawhide once some other
issues are sorted out.

Comment 2 Miloslav Trmač 2006-01-11 14:13:13 UTC
xargs -I works in FC4 findutils-4.2.20-1.


Note You need to log in before you can comment on or make changes to this bug.