I was a DOS ‘programmer’ long before I migrated to Linux - the same way some guy who used to write bat files with environment variables and errorlevel commands might migrate to a shell script.
What I really wanted was to be able to embed ^g into the Linux command line prompt, but so far I haven’t been able to. On DOS I could add ^g (the Bell character) to the prompt so each time a command finished it beeped.
I have a slightly more advanced setup which uses post-command hooks to send a desktop notification when a command has been running for over 3 seconds. That notification contains the elapsed time and the exit code too, and plays a different sound depending on whether the command was successful or not. This allows for some neat integrations with KDE connect to let me know when some long compile has finished or something even when I’m away from my computer. You can see how it works here.
I had to do some really wacky stuff but I finally got all manner of beeps and boops from the motherboard speaker last month (aftermarket addon). Stuff like beep on startup, buzz when moving a window, different quick peeps when clicking, doubleclicking or right clicking. I had it for about an afternoon and then my partner raged at all the noise :/ now my computer are silent and boring again
I vaguely recall that typing ‘copy con clock$’ would freeze a computer.
On DOS you could also have fun by replacing prompt $p$g with prompt {whatever text you want instead of c:}
Righto :)
I was a DOS ‘programmer’ long before I migrated to Linux - the same way some guy who used to write bat files with environment variables and errorlevel commands might migrate to a shell script.
What I really wanted was to be able to embed ^g into the Linux command line prompt, but so far I haven’t been able to. On DOS I could add ^g (the Bell character) to the prompt so each time a command finished it beeped.
On old unix systems, you could rename /dev/null and symlink /dev/audio to /dev/null…
Then you just had to wait.
I have a slightly more advanced setup which uses post-command hooks to send a desktop notification when a command has been running for over 3 seconds. That notification contains the elapsed time and the exit code too, and plays a different sound depending on whether the command was successful or not. This allows for some neat integrations with KDE connect to let me know when some long compile has finished or something even when I’m away from my computer. You can see how it works here.
I had to do some really wacky stuff but I finally got all manner of beeps and boops from the motherboard speaker last month (aftermarket addon). Stuff like beep on startup, buzz when moving a window, different quick peeps when clicking, doubleclicking or right clicking. I had it for about an afternoon and then my partner raged at all the noise :/ now my computer are silent and boring again
Now you need a proximity sensor to mute it only when your partner is nearby :)
Mine is still tolerating my "Eddie Izzard covered in bees person on the street reaction sound’ sms notification sound.
I’m pretty sure Konsole has a setting for that
I’ll have a hunt later. The work laptop is Ubuntu so might not be as flexible. Home is Debian for now.
I’m pretty sure it’s under the View menu