From: Christian Mallwitz <c.mallwitz@intershop.de>
To: cygwin@sourceware.cygnus.com
Subject: RE: Beeping in bash. (Again)
Date: Wed, 02 Jun 1999 09:33:00 -0000 [thread overview]
Message-ID: <F46A361BD64FD211AABC0060B0689A8024E8C9@Jena00> (raw)
Hi everybody,
> -----Original Message-----
> From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
> Sent: Wednesday, June 02, 1999 17:13
> To: Demmer, Thomas; Eric Pree; cygwin@sourceware.cygnus.com
> Subject: RE: Beeping in bash. (Again)
>
> --- "Demmer, Thomas" <TDemmer@kjs.com> wrote:
> > Not sure if that is still an issue, but
> > has the home directory have to be on a
> > binary mount? I have and it works.
>
> Oh, it's always an issue. I have text mounts but my .inputrc
> file contains no
> \r characters. This could well indeed be the reason that it
> works for some and
> not others.
If that's the reason why my .inputrc never works I f... up.
My home directory is mounted text!=binary. Both my .bashrc and .inputrc
contain \r but my .bashrc works fine ...
THIS SHOULD GO INTO THE BASH (OR CYGWIN) FAQ !!!
Cheers
Christian
--
Christian Mallwitz INTERSHOP Communications Germany
Senior Software Engineer phone: +49 3641 894 334
pgp: 02 30 7E 1A 7A C1 5C 16 2B 4D 53 A9 1B 05 F7 DD
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Christian Mallwitz <c.mallwitz@intershop.de>
To: cygwin@sourceware.cygnus.com
Subject: RE: Beeping in bash. (Again)
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <F46A361BD64FD211AABC0060B0689A8024E8C9@Jena00> (raw)
Message-ID: <19990630221000.YkcS1Vz4TIZvmboC4pr16epC4xk0ih5IwXSf_WQmuvc@z> (raw)
Hi everybody,
> -----Original Message-----
> From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
> Sent: Wednesday, June 02, 1999 17:13
> To: Demmer, Thomas; Eric Pree; cygwin@sourceware.cygnus.com
> Subject: RE: Beeping in bash. (Again)
>
> --- "Demmer, Thomas" <TDemmer@kjs.com> wrote:
> > Not sure if that is still an issue, but
> > has the home directory have to be on a
> > binary mount? I have and it works.
>
> Oh, it's always an issue. I have text mounts but my .inputrc
> file contains no
> \r characters. This could well indeed be the reason that it
> works for some and
> not others.
If that's the reason why my .inputrc never works I f... up.
My home directory is mounted text!=binary. Both my .bashrc and .inputrc
contain \r but my .bashrc works fine ...
THIS SHOULD GO INTO THE BASH (OR CYGWIN) FAQ !!!
Cheers
Christian
--
Christian Mallwitz INTERSHOP Communications Germany
Senior Software Engineer phone: +49 3641 894 334
pgp: 02 30 7E 1A 7A C1 5C 16 2B 4D 53 A9 1B 05 F7 DD
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-06-02 9:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-02 9:33 Christian Mallwitz [this message]
1999-06-30 22:10 ` Christian Mallwitz
-- strict thread matches above, loose matches on Subject: below --
1999-06-02 10:03 Earnie Boyd
1999-06-02 18:04 ` Pierre A. Humblet
1999-06-30 22:10 ` Pierre A. Humblet
1999-06-30 22:10 ` Earnie Boyd
1999-06-02 8:13 Earnie Boyd
1999-06-30 22:10 ` Earnie Boyd
1999-06-02 7:14 Earnie Boyd
1999-06-02 7:53 ` Chet Ramey
1999-06-02 9:50 ` Eric Pree
1999-06-30 22:10 ` Eric Pree
1999-06-30 22:10 ` Chet Ramey
1999-06-30 22:10 ` Earnie Boyd
1999-06-02 0:07 Keith Starsmeare
1999-06-02 6:52 ` Eric Pree
1999-06-30 22:10 ` Eric Pree
1999-06-30 22:10 ` Keith Starsmeare
1999-06-01 18:55 Earnie Boyd
1999-06-30 22:10 ` Earnie Boyd
1999-06-01 18:12 Eric Pree
1999-06-30 22:10 ` Eric Pree
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=F46A361BD64FD211AABC0060B0689A8024E8C9@Jena00 \
--to=c.mallwitz@intershop.de \
--cc=cygwin@sourceware.cygnus.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).