X-Spam-Check-By: sourceware.org
From: "Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To: <cygwin AT cygwin DOT com>
Subject: RE: potential fix for cygwin's "no system bell" problem
Date: Tue, 3 Jan 2006 18:24:44 -0600
Message-ID: <003d01c610c5$43d40d10$020aa8c0@DFW5RB41>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20060103225244.GB15348@trixie.casa.cgf.cx>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

[snip]
> >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

I must have missed something - did "MessageBeep(-1)" never get put in?  Or
did it stop working?  MSDN still documents it as working even without a
sound card.

-- 
Gary R. Van Sickle



--
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/