4 ms·
Ctrl-G still beeps your console doesn't it?
by 13of40 3y ago
Ctrl-G still beeps your console doesn't it?
- jmholla 3y agoIt doesn't on mine and I'm not sure why.
- quesera 3y agoMany terminal emulators have a config option to disable audible bell. Some have the option to replace it with a "visual bell".
- toast0 3y agoSome terminal emulators on PCs beep the PC speaker, rather than play a sound through the (high fidelity) audio device. But many PCs no longer have a PC speaker; one way to get a visual bell if the PC speaker output is used, is to connect the power LED to the speaker pins. Makes the power LED a lot more useful too.
- gpderetta 3y agoI remember speakerectomy being a thing circa 15-20 year ago, to reliably get rid of the console beep. Most MB still have speaker connections, just have nothing connected to it by default. A couple of years ago I bought a speaker off Amazon (actually a pack of 12 for 1£ as that was the minimum order) just to decode the POST beep when troubleshooting some overclocking issues. Of course I promptly removed it when finished.
- csdvrx 3y ago> Of course I promptly removed it when finished. Why? Which issues was it causing if you have the visual bell option in your terminal?
- deleted 3y ago[deleted]
- jmholla 3y agoSadly I checked that and it still doesn't work. I'm using guake on mint.
- kps 3y agoOn Linux the terminal is probably using the X11 bell, and many/most distros don't bother to hook that up. On Debian 12 you need to install `libpipewire-0.3-modules-x11` and `systemctl --user restart pipewire.service` for minimal functionality (`xset b` doesn't work).