Re: bell after incomplete completion

Re: bell after incomplete completion

[kulack]

No, that isn't the right setting. Its an actual bell, (i.e. the sound you
get when you hit C-g).
I've been trying to get ~/.initrc to work using the preference 'set
prefer-visible-bell On', but bash doesn't seem to use that file.
The readline info is the correct stuff to be looking at right? Bash uses
that for completion and keys?
Anyone know of B20 problems or common luser errors related to this?
Thanks


"Matthew Brown" <mbrown@mediadb.net> on 01/24/2000 02:03:41 PM

To:   Fred Kulack/Rochester/IBM@IBMUS, cygwin@sourceware.cygnus.com
cc:
Subject:  Re: bell after incomplete completion




In the "sounds" control panel, change the setting for "Default Beep".

-- Matthew Brown

----- Original Message -----
From: <kulack@us.ibm.com>
To: <cygwin@sourceware.cygnus.com>
Sent: Monday, January 24, 2000 3:00 PM
Subject: bell after incomplete completion


> Any way to get rid of the bell that occurs on an incomplete filename
> completion?
> Perhaps change its sound, or always prompt with the list of possible
> completions?
> I always use filename completion, and the bell is just about intolerable.
> Thanks
>
> "\C-i": complete
>
>
>
> --
> 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

Re: bell after incomplete completion

[Earnie Boyd]

--- kulack@us.ibm.com wrote:
> No, that isn't the right setting. Its an actual bell, (i.e. the sound you
> get when you hit C-g).
> I've been trying to get ~/.initrc to work using the preference 'set
> prefer-visible-bell On', but bash doesn't seem to use that file.
> The readline info is the correct stuff to be looking at right? Bash uses
> that for completion and keys?
> Anyone know of B20 problems or common luser errors related to this?

Readline is the correct place to be looking.  I don't remember if the visible
bell works but you can turn the bell off.  If you had searched the archives you
would have found that the ~/.initrc must be a UNIX format file.  I.E.: it must
contain \n line endings and not \r\n line endings.

Earnie.

=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Cygwin Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: bell after incomplete completion

[Matthew Brown]

In the "sounds" control panel, change the setting for "Default Beep".

-- Matthew Brown

----- Original Message ----- 
From: <kulack@us.ibm.com>
To: <cygwin@sourceware.cygnus.com>
Sent: Monday, January 24, 2000 3:00 PM
Subject: bell after incomplete completion


> Any way to get rid of the bell that occurs on an incomplete filename
> completion?
> Perhaps change its sound, or always prompt with the list of possible
> completions?
> I always use filename completion, and the bell is just about intolerable.
> Thanks
> 
> "\C-i": complete
> 
> 
> 
> --
> 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

bell after incomplete completion

[kulack]

Any way to get rid of the bell that occurs on an incomplete filename
completion?
Perhaps change its sound, or always prompt with the list of possible
completions?
I always use filename completion, and the bell is just about intolerable.
Thanks

"\C-i": complete



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com