Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Kill bell_beeps setting (or make it a no-op) #524
It doesn't do what people think it does.
People enable it expecting it to enable beeps when they get highlighted. It's not for that.
It's for beeping when anyone in any window sends a ^G character (ascii bell) - and that's without changing the activity level of the window in which it happened.
It's dumb and only trolls ever use it. Also, plenty of guides suggest people to turn it on, ignoring the real effect of doing so.
Any objections to nuke it? Any useful purpose for this setting that I'm missing?
EDIT FROM THE FAR FUTURE:
THIS IS NOT ABOUT SENDING THE BELL CHARACTER TO YOUR TERMINAL WHEN YOU GET HIGHLIGHTED OR GET PRIVATE MESSAGES
NOT HAVING THIS SETTING DOES NOT REMOVE THE ABILITY TO GET BEEPS
YOU DO NOT NEED THIS SETTING
(Sorry for the caps, not mad or anything, but somehow we still get people regularly complaining about this, even people who have seen this ticket.)
I really doubt it can be useful ever. A "maybe" isn't enough. I'm looking for concrete use cases, if they even exist.
Also, even that name is ambiguous. For example, in one of the pages that suggests enabling this, someone tried to explain how enabling this setting is a bad idea, by saying "It actually does something far worse. It makes the beep control code send a beep to your terminal", and the author of the post replied:
To be fair, it wasn't the best explanation of the issue, but it was ambiguous in the same way that