-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Eric Blake on 3/19/2007 7:02 AM:
> Thanks for the report, and I'm still investigating. But it appears you
> are using cmd.com based on $TERM=cygwin. And in the readline source code,
> even if visible bells are requested, readline falls back on an audible
> bell if it can't figure out how to do a visible alert on your terminal.
> Therefore, my guess is that the cygwin termcap/terminfo entry lacks
> whatever string causes a visible bell (and more likely, the cygwin tty
> code lacks support for visible alerts altogether).
Sure enough:
$ infocmp -d cygwin xterm | grep flash
flash: NULL, '\E[?5h$<100/>\E[?5l'.
ie. there is currently no visible alert support in the cygwin terminfo, so
if you don't use rxvt or xterm, 'set bell-style visible' is currently
synonymous with 'set bell-style audible', and there's nothing I can do
about it in readline. Patches to cygwin1.dll and to the cygwin terminfo
entry are welcome, but I won't be writing them.
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF/o9t84KuGfSFAYARApRIAJ9HDYJvgXkRpIHy2JgVXThcDul1RwCfTfGg
396Q2PLsdQZRU5vSnENDdC8=
=iTVb
-----END PGP SIGNATURE-----
--
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/
