This is the mail archive of the
mailing list for the Cygwin project.
RE: potential fix for cygwin's "no system bell" problem
- From: "Gary R. Van Sickle" <g dot r dot vansickle at worldnet dot att dot net>
- To: <cygwin at cygwin dot com>
- Date: Tue, 3 Jan 2006 18:24:44 -0600
- Subject: RE: potential fix for cygwin's "no system bell" problem
> >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:
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
Gary R. Van Sickle
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html