This is the mail archive of the
mailing list for the Cygwin project.
Re: .bashrc strange behavior
- To: firstname.lastname@example.org, email@example.com
- Subject: Re: .bashrc strange behavior
- From: Earnie Boyd <firstname.lastname@example.org>
- Date: Mon, 19 Jul 1999 18:23:51 -0400 (EDT)
- Reply-To: email@example.com
This problem is related to the text vs binary issue. The user has the files
mounted in binary mode. The .bashrc has \r\n (or text mode) line endings. The
\r is being input into the buffer instead of removed causing the problems you
This is the reason I preach leaving the default text mounts and properly
porting the code specifying the processing mode.
--- Kevin Plyler <firstname.lastname@example.org> wrote:
> I hope this is a simple one, I could not find anything related in the mail
> We have several PC here running NT4.0SP4
> with Cygwin32 B20.1
> one person's $HOME/.bashrc behaves rather strangely
> (blank lines are given :command not found, aliases get garbled,
> 'type' does not work ...)
> Here is the begining of some testing I was doing in his .bashrc:
> bash-2.02$ cat .bashrc
> #alias ll='ls -la'
> echo 1
> alias r='c -e -'
> echo 2
> echo 3
> type ls
> type alias
> bash-2.02$ . .bashrc
> : command not found
> : not found ls
> : not found alias
> bash-2.02$ alias
> 'lias r='c -e -
> I have set:
> CYGWIN='binmode tty'
> any suggestions?
> "You have just won an all expenses paid vacation to Hawaii for 2 weeks!"
> I got that call! Except it's a place infinitely better than Hawaii, and
> infinitely longer than two weeks. -- II Corinthians 5:1
> Kevin Plyler, AG Communication Systems Phoenix AZ. 85027
> Phone: 1 (623) 582-7670; FAX: 581-4884 / E-mail: email@example.com
> Want to unsubscribe from this list?
> Send a message to firstname.lastname@example.org
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Want to unsubscribe from this list?
Send a message to email@example.com