Message-ID: <4515D901.3020809@byu.net>
Date: Sat, 23 Sep 2006 19:01:53 -0600
From: Eric Blake <ebb9@byu.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin@cygwin.com, logsnaath@gmx.net
Subject: Re: tr command suddenly behaves differently
References: <1026800198.20060923122829@ukr.name> <002801c6defd$93958660$140110ac@LOGUCO>
In-Reply-To: <002801c6defd$93958660$140110ac@LOGUCO>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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             ebb9@byu.net
volunteer cygwin bash maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFFdkB84KuGfSFAYARAiMQAJ44gGiyngMpZ5qIn8hE/3gAsmD4VQCfbMHd
U6W30ICqcIH9boe7zPWgi4M=
=yDM0
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/