Re: tr command suddenly behaves differently

2006-09-24 Thread Larry Hall (Cygwin)
Logu wrote: One final point. It's considered bad netiquette to commandeer another thread. Replying to another's message and changing the subject is not the way to post to this list. Please just send email to the list directly when you want to start some new topic. It makes following a thre

Re: tr command suddenly behaves differently

2006-09-24 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jim Easton on 9/24/2006 1:02 AM: > Pardon me for putting my oar in but the syntax of tr varies quite a > bit from system to system. It has been my experience that the only > reliable way of expressing the above so that it will work on cyg

Re: tr command suddenly behaves differently

2006-09-24 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Logu on 9/24/2006 12:12 AM: > The /etc/profile had this code hence I thought it is bug in the cygwin > system. May be this is fixed in the newer versions. > - > case "`echo "$0" | /usr/bin/tr [:upper:] [:lower:]

Re: tr command suddenly behaves differently

2006-09-24 Thread Jim Easton
Hi, > 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:] Sat, 23 Sep 2006 Eric Blake wrote > There's your problem. You didn't quote properly. Try: > $ echo [:upper:] [:lower:] >

Re: tr command suddenly behaves differently

2006-09-23 Thread Logu
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

Re: tr command suddenly behaves differently

2006-09-23 Thread Logu
One final point. It's considered bad netiquette to commandeer another thread. Replying to another's message and changing the subject is not the way to post to this list. Please just send email to the list directly when you want to start some new topic. It makes following a thread much easier

Re: tr command suddenly behaves differently

2006-09-23 Thread Eric Blake
-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 se

Re: tr command suddenly behaves differently

2006-09-23 Thread Larry Hall (Cygwin)
Logu wrote: Hi, I an using cygwin (CYGWIN_NT-5.1 LOGU-CO 1.5.11(0.116/4/2) 2004-09-04 23:17 i686 unknown unknown Cygwin) on Windows Xp Professional Edition. All of a sudden the tr (/usr/bin/tr) command started working differently. So when I login through ssh I get an error message as follow

Re: tr command suddenly behaves differently

2006-09-23 Thread Logu
Hi, I an using cygwin (CYGWIN_NT-5.1 LOGU-CO 1.5.11(0.116/4/2) 2004-09-04 23:17 i686 unknown unknown Cygwin) on Windows Xp Professional Edition. All of a sudden the tr (/usr/bin/tr) command started working differently. So when I login through ssh I get an error message as follows while loggi

tr command suddenly behaves differently

2006-09-23 Thread Logu
Hi, I an using cygwin (CYGWIN_NT-5.1 LOGU-CO 1.5.11(0.116/4/2) 2004-09-04 23:17 i686 unknown unknown Cygwin) on Windows Xp Professional Edition. All of a sudden the tr (/usr/bin/tr) command started working differently. So when I login through ssh I get an error message as follows while logging