[bug #44570] Wrong find -type f -not -name "*txt" result for files with weird names

Follow-up Comment #2, bug #44570 (project findutils): Yes, LC_ALL=C solved this problem. It is not a bug in 'find'. Thank you! ___ Reply to this item at:

[bug #44570] Wrong find -type f -not -name "*txt" result for files with weird names

Follow-up Comment #1, bug #44570 (project findutils): Try again, using: LC_ALL=C find -type f -not -name '*.txt' My guess is that you are in a non-C multibyte locale, and that the filenames being printed are ones that are invalid when interpreted in the multibyte encoding rules of your current lo

[bug #44570] Wrong find -type f -not -name "*txt" result for files with weird names

URL: Summary: Wrong find -type f -not -name "*txt" result for files with weird names Project: findutils Submitted by: kotu88 Submitted on: Wed 18 Mar 2015 02:29:04 PM GMT Category: fin

[bug #44569] find newermt cannot figure out how to interpret some dates.

Update of bug #44569 (project findutils): Status:None => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #1: This is not a bug

[bug #44569] find newermt cannot figure out how to interpret some dates.

URL: Summary: find newermt cannot figure out how to interpret some dates. Project: findutils Submitted by: andreyoliveira Submitted on: Qua 18 Mar 2015 14:04:33 GMT Category: find