On Mon, 2 Jan 2006, Christopher Faylor wrote:
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
On Tue, Jan 03, 2006 at 02:12:13PM -0500, Igor Peshansky wrote:
FWIW, this will only work on WinXP. Win2k uses 'ding.wav' instead.
'ding.wav' is also present on XP, so as a catch-all solution, using that
may be better.
Maybe you should have checked on the current state of the sources before
On Tue, 3 Jan 2006, Christopher Faylor wrote:
On Tue, Jan 03, 2006 at 02:12:13PM -0500, Igor Peshansky wrote:
FWIW, this will only work on WinXP. Win2k uses 'ding.wav' instead.
'ding.wav' is also present on XP, so as a catch-all solution, using that
may be better.
Maybe you should have
On Tue, 3 Jan 2006, Christopher Faylor wrote:
On Tue, Jan 03, 2006 at 02:12:13PM -0500, Igor Peshansky wrote:
FWIW, this will only work on WinXP. Win2k uses 'ding.wav' instead.
'ding.wav' is also present on XP, so as a catch-all solution, using that
may be better.
Maybe you should have
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
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,
[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
On Tue, Jan 03, 2006 at 06:24:44PM -0600, Gary R. Van Sickle wrote:
[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
[snip]
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.
It got put in but it didn't work for everyone. And, for some
people, like me, it worked for a while and then stopped.
9 matches
Mail list logo
