From: "Suhaib M. Siddiqi" <ssiddiqi@ipass.net>
To: <plylerk@agcs.com>, <cygwin@sourceware.cygnus.com>
Subject: RE: .bashrc strange behavior
Date: Sat, 31 Jul 1999 18:34:00 -0000 [thread overview]
Message-ID: <LOBBLPGIHMIEGBEAFDMCMEFGCAAA.ssiddiqi@ipass.net> (raw)
Message-ID: <19990731183400.B7XGFn9qSGNbTICwpKJRj9qoTdzodzeDRBQo2DNV4pA@z> (raw)
In-Reply-To: <3793A0DC.83DCBB22@agcs.com>
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
next prev parent reply other threads:[~1999-07-31 18:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-19 15:04 Kevin Plyler
1999-07-19 17:59 ` Suhaib M. Siddiqi [this message]
1999-07-31 18:34 ` Suhaib M. Siddiqi
1999-07-31 18:34 ` Kevin Plyler
1999-07-19 15:23 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=LOBBLPGIHMIEGBEAFDMCMEFGCAAA.ssiddiqi@ipass.net \
--to=ssiddiqi@ipass.net \
--cc=cygwin@sourceware.cygnus.com \
--cc=plylerk@agcs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).