* Re: .bashrc strange behavior
@ 1999-07-19 15:23 Earnie Boyd
1999-07-19 16:10 ` Ian T Zimmerman
1999-07-31 18:34 ` Earnie Boyd
0 siblings, 2 replies; 10+ messages in thread
From: Earnie Boyd @ 1999-07-19 15:23 UTC (permalink / raw)
To: plylerk, cygwin
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
are seeing.
This is the reason I preach leaving the default text mounts and properly
porting the code specifying the processing mode.
Earnie.
--- Kevin Plyler <plylerk@agcs.com> wrote:
> I hope this is a simple one, I could not find anything related in the mail
> archive.
>
> 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
> 1
> 2
> : command not found
> 3
> : not found ls
> : not found alias
> bash-2.02$ alias
> 'lias r='c -e -
>
> I have set:
> CYGWIN='binmode tty'
>
> any suggestions?
>
> Thanks
>
> --
> "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: plylerk@agcs.com
>
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: .bashrc strange behavior
1999-07-19 15:23 .bashrc strange behavior Earnie Boyd
@ 1999-07-19 16:10 ` Ian T Zimmerman
1999-07-19 17:57 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-31 18:34 ` Earnie Boyd
1 sibling, 2 replies; 10+ messages in thread
From: Ian T Zimmerman @ 1999-07-19 16:10 UTC (permalink / raw)
To: cygwin
>>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes:
Earnie> This problem is related to the text vs binary issue. The
Earnie> user has the files mounted in binary mode. The .bashrc
Earnie> has \r\n (or text mode) line endings. The \r is being
Earnie> input into the buffer instead of removed causing the
Earnie> problems you are seeing.
Earnie> This is the reason I preach leaving the default text
Earnie> mounts and properly porting the code specifying the
Earnie> processing mode.
... but of course this wouldn't happen were .bashrc created by a
Cygwin program. They probably created it with Notepad or something.
IMHO there should be a fat warning about this in the User Guide. It
is mentioned there already, but too softly.
:-)
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: .bashrc strange behavior
1999-07-19 16:10 ` Ian T Zimmerman
@ 1999-07-19 17:57 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Ian T Zimmerman
1 sibling, 1 reply; 10+ messages in thread
From: Suhaib M. Siddiqi @ 1999-07-19 17:57 UTC (permalink / raw)
To: Ian T Zimmerman, cygwin
>
> >>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes:
>
> Earnie> This problem is related to the text vs binary issue. The
> Earnie> user has the files mounted in binary mode. The .bashrc
> Earnie> has \r\n (or text mode) line endings. The \r is being
> Earnie> input into the buffer instead of removed causing the
> Earnie> problems you are seeing.
>
> Earnie> This is the reason I preach leaving the default text
> Earnie> mounts and properly porting the code specifying the
> Earnie> processing mode.
>
> ... but of course this wouldn't happen were .bashrc created by a
> Cygwin program. They probably created it with Notepad or something.
> IMHO there should be a fat warning about this in the User Guide. It
> is mentioned there already, but too softly.
>
> :-)
>
better to leave the defaults, that will save you a lot of time on which
editor to use
Notepad or vi.
Suhaib
> --
> Ian Zimmerman
> Lightbinders, Inc.
> 2325 3rd Street #324, San Francisco, California 94107
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: .bashrc strange behavior
1999-07-19 15:23 .bashrc strange behavior Earnie Boyd
1999-07-19 16:10 ` Ian T Zimmerman
@ 1999-07-31 18:34 ` Earnie Boyd
1 sibling, 0 replies; 10+ messages in thread
From: Earnie Boyd @ 1999-07-31 18:34 UTC (permalink / raw)
To: plylerk, cygwin
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
are seeing.
This is the reason I preach leaving the default text mounts and properly
porting the code specifying the processing mode.
Earnie.
--- Kevin Plyler <plylerk@agcs.com> wrote:
> I hope this is a simple one, I could not find anything related in the mail
> archive.
>
> 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
> 1
> 2
> : command not found
> 3
> : not found ls
> : not found alias
> bash-2.02$ alias
> 'lias r='c -e -
>
> I have set:
> CYGWIN='binmode tty'
>
> any suggestions?
>
> Thanks
>
> --
> "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: plylerk@agcs.com
>
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: .bashrc strange behavior
1999-07-19 17:57 ` Suhaib M. Siddiqi
@ 1999-07-31 18:34 ` Suhaib M. Siddiqi
0 siblings, 0 replies; 10+ messages in thread
From: Suhaib M. Siddiqi @ 1999-07-31 18:34 UTC (permalink / raw)
To: Ian T Zimmerman, cygwin
>
> >>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes:
>
> Earnie> This problem is related to the text vs binary issue. The
> Earnie> user has the files mounted in binary mode. The .bashrc
> Earnie> has \r\n (or text mode) line endings. The \r is being
> Earnie> input into the buffer instead of removed causing the
> Earnie> problems you are seeing.
>
> Earnie> This is the reason I preach leaving the default text
> Earnie> mounts and properly porting the code specifying the
> Earnie> processing mode.
>
> ... but of course this wouldn't happen were .bashrc created by a
> Cygwin program. They probably created it with Notepad or something.
> IMHO there should be a fat warning about this in the User Guide. It
> is mentioned there already, but too softly.
>
> :-)
>
better to leave the defaults, that will save you a lot of time on which
editor to use
Notepad or vi.
Suhaib
> --
> Ian Zimmerman
> Lightbinders, Inc.
> 2325 3rd Street #324, San Francisco, California 94107
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: .bashrc strange behavior
1999-07-19 16:10 ` Ian T Zimmerman
1999-07-19 17:57 ` Suhaib M. Siddiqi
@ 1999-07-31 18:34 ` Ian T Zimmerman
1 sibling, 0 replies; 10+ messages in thread
From: Ian T Zimmerman @ 1999-07-31 18:34 UTC (permalink / raw)
To: cygwin
>>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes:
Earnie> This problem is related to the text vs binary issue. The
Earnie> user has the files mounted in binary mode. The .bashrc
Earnie> has \r\n (or text mode) line endings. The \r is being
Earnie> input into the buffer instead of removed causing the
Earnie> problems you are seeing.
Earnie> This is the reason I preach leaving the default text
Earnie> mounts and properly porting the code specifying the
Earnie> processing mode.
... but of course this wouldn't happen were .bashrc created by a
Cygwin program. They probably created it with Notepad or something.
IMHO there should be a fat warning about this in the User Guide. It
is mentioned there already, but too softly.
:-)
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* .bashrc strange behavior
1999-07-19 15:04 Kevin Plyler
1999-07-19 17:59 ` Suhaib M. Siddiqi
@ 1999-07-31 18:34 ` Kevin Plyler
1 sibling, 0 replies; 10+ messages in thread
From: Kevin Plyler @ 1999-07-31 18:34 UTC (permalink / raw)
To: cygwin
I hope this is a simple one, I could not find anything related in the mail archive.
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
1
2
: command not found
3
: not found ls
: not found alias
bash-2.02$ alias
'lias r='c -e -
I have set:
CYGWIN='binmode tty'
any suggestions?
Thanks
--
"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: plylerk@agcs.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: .bashrc strange behavior
1999-07-19 17:59 ` Suhaib M. Siddiqi
@ 1999-07-31 18:34 ` Suhaib M. Siddiqi
0 siblings, 0 replies; 10+ messages in thread
From: Suhaib M. Siddiqi @ 1999-07-31 18:34 UTC (permalink / raw)
To: plylerk, cygwin
This is a text vs binary mount issue. I believe user had a binary mounted
disk.
> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Kevin Plyler
> Sent: Monday, July 19, 1999 6:04 PM
> To: cygwin@sourceware.cygnus.com
> Subject: .bashrc strange behavior
>
>
> I hope this is a simple one, I could not find anything related in
> the mail archive.
>
> 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
> 1
> 2
> : command not found
> 3
> : not found ls
> : not found alias
> bash-2.02$ alias
> 'lias r='c -e -
>
> I have set:
> CYGWIN='binmode tty'
>
> any suggestions?
>
> Thanks
>
> --
> "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: plylerk@agcs.com
>
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: .bashrc strange behavior
1999-07-19 15:04 Kevin Plyler
@ 1999-07-19 17:59 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Kevin Plyler
1 sibling, 1 reply; 10+ messages in thread
From: Suhaib M. Siddiqi @ 1999-07-19 17:59 UTC (permalink / raw)
To: plylerk, cygwin
This is a text vs binary mount issue. I believe user had a binary mounted
disk.
> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Kevin Plyler
> Sent: Monday, July 19, 1999 6:04 PM
> To: cygwin@sourceware.cygnus.com
> Subject: .bashrc strange behavior
>
>
> I hope this is a simple one, I could not find anything related in
> the mail archive.
>
> 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
> 1
> 2
> : command not found
> 3
> : not found ls
> : not found alias
> bash-2.02$ alias
> 'lias r='c -e -
>
> I have set:
> CYGWIN='binmode tty'
>
> any suggestions?
>
> Thanks
>
> --
> "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: plylerk@agcs.com
>
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 10+ messages in thread
* .bashrc strange behavior
@ 1999-07-19 15:04 Kevin Plyler
1999-07-19 17:59 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Kevin Plyler
0 siblings, 2 replies; 10+ messages in thread
From: Kevin Plyler @ 1999-07-19 15:04 UTC (permalink / raw)
To: cygwin
I hope this is a simple one, I could not find anything related in the mail archive.
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
1
2
: command not found
3
: not found ls
: not found alias
bash-2.02$ alias
'lias r='c -e -
I have set:
CYGWIN='binmode tty'
any suggestions?
Thanks
--
"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: plylerk@agcs.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~1999-07-31 18:34 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-07-19 15:23 .bashrc strange behavior Earnie Boyd
1999-07-19 16:10 ` Ian T Zimmerman
1999-07-19 17:57 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-31 18:34 ` Earnie Boyd
-- strict thread matches above, loose matches on Subject: below --
1999-07-19 15:04 Kevin Plyler
1999-07-19 17:59 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Kevin Plyler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).