Date: Mon, 2 Jan 2006 20:33:55 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: potential fix for cygwin's "no system bell" problem
Message-ID: <20060103013355.GA14262@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

I've just built a cygwin snapshot which should work around a problem
with Cygwin's default bell not working.  This was discussed here a while
ago:

http://www.cygwin.com/ml/cygwin/2004-03/threads.html#00895
http://www.cygwin.com/ml/cygwin/2004-03/threads.html#00966

(and it may have even been mentioned more recently for all that I
know)

And Lev Bishop posted a fix even earlier:

http://www.cygwin.com/ml/cygwin/2003-05/msg01615.html

This problem is apparently more prevalent than I had thought so my
decision not to do anything about it in 2004 was wrong.

I stumbled into this conclusion because someone was trying to figure out
what was going wrong on the cygwin irc channel on freenode.net today
and, on testing, it was discovered that neither Corinna nor I had a
working bell anymore, either.  So, rather than make this a FAQ, as
suggested by Igor in the 2004 thread, I thought it would be best to just
fix the problem in cygwin itself.

The snapshot uses Lev's method to reinstate the default bell.  If there
are other causes for this problem then they won't be fixed by this
method but this seems to rectify things for me.

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/