× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



when processing an express (f. e. ls /tmp/*.pdf)

Not exactly true, and this has always bugged me. Say our current directory
is in a non-case-sensitive FS, and we have two files there:
file1.txt
file2.TXT

Interestingly, I can do: cat file2.txt and the system will dutifully echo
the content of the file. Same with cat FILE1.TXT. OK so far.

BUT, if I try this: ls *.txt then I get only one line output: file1.txt.
If I do: ls *.TXT, I get only one line output, and of course it is
file2.TXT

I find this frustrating and inconsistent and have always felt that IBM
should fix it.

BTW: to do a case insensitive ls for files with txt extension, you could do:
ls *.[Tt][Xx][Tt]


Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"The income tax has made more liars out of American people than golf has."
-- Will Rogers




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.