X-Spam-Check-By: sourceware.org Date: Tue, 3 Jan 2006 17:52:44 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: potential fix for cygwin's "no system bell" problem Message-ID: <20060103225244.GB15348@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20060103013355.GA14262@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Tue, Jan 03, 2006 at 02:39:51PM -0800, Shankar Unni wrote: >Christopher Faylor wrote: > >>http://www.cygwin.com/ml/cygwin/2003-05/msg01615.html > >So I just installed snapshot 20060103. I'm running WinXP SP2. > >Before I installed the snapshot, I didn't have that >...\Apps\.Default\.Default key at all, and the beep apparently still >worked for CMD. Now, I have this key, and the (Default) entry is set to >"ding.wav". > >CMD.EXE still issues an actual beep (PC-beeper-beep) when I type > > echo ^G (literal control g) > >(This is using CMD's built-in echo). > >bash and tcsh now emit a "ding" instead, for the same command (using >shell builtins). > >(I guess I'm wondering if this is to be the expected behavior from now >on; is there any way now to get bash and tcsh to emit a real beep?) This is the way it was has been intended to work for almost two years: http://cygwin.com/ml/cygwin-patches/2003-q1/threads.html#00203 cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/