tr command suddenly behaves differently
Sun Sep 24 01:01:00 GMT 2006
-----BEGIN PGP SIGNED MESSAGE-----
According to Logu on 9/23/2006 4:46 AM:
> After analysing I found that the tr command did not work correctly. So
> the command
> $ /usr/bin/tr [:upper:] [:lower:]
There's your problem. You didn't quote properly. Try:
$ echo [:upper:] [:lower:]
to see what you were really invoking, then try:
$ tr '[:upper:]' '[:lower:]'
to do what you meant.
My guess is that you have a file in your home directory that uses a single
letter, so the bracket expansion of bash took effect and expanded to that
filename rather than passing through the regex that you thought you typed.
By the way, none of this is cygwin specific.
Life is short - so eat dessert first!
Eric Blake firstname.lastname@example.org
volunteer cygwin bash maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v22.214.171.124 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin