Fri, 13 May 2016 18:13:27 +0900 Bryan Linton <b...@shoshoni.info> > On 2016-05-13 00:56:52, Ted Unangst <t...@tedunangst.com> wrote: > > 1. I have wsconsctl keyboard.bell.volume=0 because I don't like things > > beeping > > at me. This recently stopped working in xterm, where I now get a loud beep. > > Related to loss of pcvt? > > > > I'm not sure where the failure is, but my expectation is that if I say the > > glass console doesn't beep, then I don't want it beeping. Somehow the beeps > > are getting routed into the audio device before wscons fixes them. > > > > 2. Even with mixerctl inputs.mix_beep=0 I still here beeps. They are softer, > > but they are not gone. My expectation is that if I set something to 0, it > > should disappear. > > I noticed this behavior too, and it really irritated me until I > figured out how to fix it. > > In my case, I had a line in .xinitrc that read: > xset b 50 440 100 > #xset b[ell] [volume] [pitch] [duration] > > Apparently, in previous versions of OpenBSD and/or X.Org/Xenocara > the wsconsctl options overrode that. I fixed it my case by > changing that line to the following: > xset b 0 440 100 > > I'm not sure if that counts as a "fix" or or "quick hack", but it > stopped the beeping for me.
The bell is an important status notification beep feedback, especially for terminal work in environments where sound devices are not present. You can for example tone it down to a short low frequency puck sound if you use high powered amplifiers, confirmed safe and unobtrusive enough but still audible so you can benefit from the presence of sound signal: $ xset b 100 20 5 What annoys people is they can't figure out what gave the bell, which they want to control or tone down a bit for their quiet room, or more the frequency and duration. Most users (kids) were not present when that bell gave thrilling sparks in young men eyes, when PCs surfaced. Once you figure usefulness of the "irritation" it becomes a necessity. It would be worthier figuring out what gave the bell, if you can't track mentally the state of too much programs running concurrently.
