Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: kulack AT us DOT ibm DOT com X-Lotus-FromDomain: IBMUS To: cygwin AT sourceware DOT cygnus DOT com Message-ID: <85256870.00755AB7.00@D51MTA08.pok.ibm.com> Date: Mon, 24 Jan 2000 15:21:41 -0600 Subject: Re: bell after incomplete completion Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline 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" on 01/24/2000 02:03:41 PM To: Fred Kulack/Rochester/IBM AT IBMUS, cygwin AT sourceware DOT cygnus DOT com cc: Subject: Re: bell after incomplete completion In the "sounds" control panel, change the setting for "Default Beep". -- Matthew Brown ----- Original Message ----- From: To: 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 AT sourceware DOT cygnus DOT com > > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com