[bug #26701] if there are any funny characters, * no longer matches in certain locales

2009-05-27 Thread INVALID.NOREPLY
URL: Summary: if there are any funny characters, * no longer matches in certain locales Project: findutils Submitted by: jidanni Submitted on: Wed May 27 21:20:32 2009 Category: find

[bug #26701] if there are any funny characters, * no longer matches in certain locales

2009-07-12 Thread INVALID.NOREPLY
Additional Item Attachment, bug #26701 (project findutils): File name: test.shSize:0 KB ___ Reply to this item at: ___ Message

[bug #26701] if there are any funny characters, * no longer matches in certain locales

2010-03-31 Thread INVALID.NOREPLY
Follow-up Comment #5, bug #26701 (project findutils): Don't you see the attached test case files? Here's even a new test case not in a file: set -eu n=/tmp/oo mkdir -p $n; cd $n #recode qp ___ Message sent via/b

[bug #26701] if there are any funny characters, * no longer matches in certain locales

2010-03-31 Thread INVALID.NOREPLY
Follow-up Comment #6, bug #26701 (project findutils): All I know is the bug is on Debian extreme latest. find (GNU findutils) 4.4.2 If it does exist for you in 4.4.2 but not later, then it is fixed. However I just use Debian so don't send source. ___

[bug #54730] Add additional valuable example of find -quit

2018-09-25 Thread INVALID.NOREPLY
URL: Summary: Add additional valuable example of find -quit Project: findutils Submitted by: jidanni Submitted on: Wed 26 Sep 2018 02:34:51 AM UTC Category: documentation

[bug #54731] On find man page mention what "sometimes" means

2018-09-25 Thread INVALID.NOREPLY
URL: Summary: On find man page mention what "sometimes" means Project: findutils Submitted by: jidanni Submitted on: Wed 26 Sep 2018 02:37:59 AM UTC Category: documentation

[bug #54730] Add additional valuable example of find -quit

2018-09-26 Thread INVALID.NOREPLY
Follow-up Comment #2, bug #54730 (project findutils): Yes there should be many examples added. The syntax error was on purpose. The idea is: use -quit as an emergency brake while perfecting one's find recipe. Let's say of every five adjustments one is a syntax error. In that case one would want

[bug #54731] On find man page mention what "sometimes" means

2018-09-26 Thread INVALID.NOREPLY
Follow-up Comment #2, bug #54731 (project findutils): OK but maybe leave one example, even if just on this bug report, so we know what this is talking about. ___ Reply to this item at:

[bug #54730] Add additional valuable example of find -quit

2018-09-27 Thread INVALID.NOREPLY
Follow-up Comment #7, bug #54730 (project findutils): You guys are brilliant. Here's some more: When just one is enough: # find /proc -name 11 -print | wc -l 178 # find /proc -name 11 -print -quit | wc -l 1 Or better yet: Where did I put that file called "needle2"? No reason to keep looking for

[bug #54730] Add additional valuable example of find -quit

2018-09-27 Thread INVALID.NOREPLY
Follow-up Comment #8, bug #54730 (project findutils): Compare with the current: "find /tmp/foo /tmp/bar -print -quit will print only /tmp/foo." ___ Reply to this item at: __

[bug #57291] xargs --verbose adds incorrect trailing blank

2019-11-22 Thread INVALID.NOREPLY
URL: Summary: xargs --verbose adds incorrect trailing blank Project: findutils Submitted by: jidanni Submitted on: Sat 23 Nov 2019 04:10:55 AM UTC Category: xargs Seve

[bug #62325] is This Typo?(xargs.1)

2022-04-16 Thread INVALID.NOREPLY
URL: Summary: is This Typo?(xargs.1) Project: findutils Submitted by: ribbon Submitted on: Sat 16 Apr 2022 11:28:30 PM UTC Category: documentation Severity: 3 - Normal