The article mentions not wanting to put a bell in their terminal prompt because it would cause too many notifications, but I found it difficult to remember to put `;tput bel` on every command that would be slow, so I compromised by configuring my shell to notify only on commands that took longer than 10 seconds. I also use a popup instead of a straight bell so I'll see a reminder of what it was that was happening (this is for MacOS, on Linux it would use `notify-send` instead):
function preexec() {
lrn_timer=${timer:-$SECONDS}
lrn_command="$1"
}
lrn_timer=0
function precmd() {
[[ -v lrn_timer ]] || return # preexec() doesn't set timer if no command run (e.g. from ^C before running)
timer_show=$(($SECONDS - $lrn_timer))
unset lrn_timer
# 10 is the notification threshold in seconds
if (( ${timer_show} > 10 )); then
terminal-notifier -sound default -message "Exit $? in ${timer_show}s: $lrn_command"
fi
}
> [...] but I found it difficult to remember to put `;tput bel` on every command that would be slow [...]
What I do in these situations (assuming the job is still in the foreground, and can be interrupted), is suspend the task with ctrl+z and resume with `fg`, chaining it with some other command:
fg; notify-send "done"
This uses the "job control" feature of `bash`, so it requires no extra setup. Your approach has the simple advantage however, that once it's set up, it just works, automatically.
One of the smart things with zsh is that the hooks¹ like precmd can be replaced with arrays of functions, so that you can cleanly have multiple hooks per hook point. It even provides a nice tool to work with the the arrays too², which makes editing/enabling/disabling far easier.
It makes life far easier when you see people post useful snippets(like wolfgang42's), but don't want to have to mangle them in to your already messy monolithic function.
(I apparently knew this when I wrote the above code, since on closer inspection it doesn’t actually match the gist my comments claim it came from, but I have to admit I had since forgotten it.)
Right, but I was asking about Bash, where this worked unchanged on my Mac...
I do actually have something installed in my env, I think, that might trigger those functions automatically if they exist, now that I think about it...
bash> v PROMPT_COMMAND
PROMPT_COMMAND is an indexed array variable
declare -a PROMPT_COMMAND=([0]=$'__bp_precmd_invoke_cmd\nmcfly_prompt_command;_direnv_hook\n:' [1]="__bp_interactive_mode")
(pretty sure that this broke when I tried to force it to be a pure array instead of a 2 element array with the first as a concatenation of functions... unfortunately)
The README for https://github.com/nowrep/notify-desktop says “It's basically clone of notify-send from libnotify” so I assume that would also work, but I don’t know your system.
I'd wanted a bell in the Rust Egui/Winit system. There's no simple cross-platform "beep" or bell feature, short of bringing up a whole audio system.
The original Teletype bell in a Model 15 Teletype is a 3-inch gong with a satisfying "bong" sound. That was intended to be heard across a room of noisy machines. There's also a little end of line bell for typists, but that's not loud.
> The original Teletype bell in a Model 15 Teletype is a 3-inch gong with a satisfying "bong" sound. That was intended to be heard across a room of noisy machines. There's also a little end of line bell for typists, but that's not loud.
What would the machine do if a mischievous prankster ran a program that endlessly outputted ASCII BEL characters in a tight loop?
I used to have a Model 43 Teletype. Sending a suitable number of BELs and then sleeping 4 seconds made for a convincing simulation of a ringing telephone.
> konsole: As far as I can tell it isn't supported. Creating a new profile and setting the "Terminal bell mode" to "Visual Bell" doesn't seem to result in the urgent hint being set.
However, Konsole has a way better solution for the presented problem: it has been possible to "monitor for (in)activity for a long time. It is also now possible to monitor for process termination, which you can (un)check anytime if you decide that you need to be notified.
These features are very convenient, much better than having to hack a solution using the bell in my opinion.
Difference is that what the author wrote is a fair bit more portable since it doesn't require the use of a separate terminal xlient. Sure, konsole is lightweight and relatively portable, but doing it in a shell this way would work regardless of the terminal.
> Bells ringing, chiming, or (as is appropriate for the season) jingling all sounds very noisy - but although you can configure your terminal emulator to emit a sound for the terminal bell, I'm actually advocating for configuring a non-intrusive but persistent visual notification.
So, not a bell (remember that noisy awfulness whenever you held backspace for a bit too long and it spammed useless warnings that there is nothing to delete)
> makes it easy to configure behaviour based on the duration of a command and
Glad the article was edited, it's indeed way more reasonable than having the mental overhead to add ;bell every time (though notifications have a benefit that you can add a payload that tells you which command finished and how long it took without having to switch back)
(Article author here). I'm typically executing the same compile command from shell history (or via an alias) so missing off the `'; bell` isn't really a concern, but I agree that automatically triggering it after commands of a certain duration is a nicer way of avoiding that mental overhead if you're executing a wider variety of commands.
I thought this was going to be an article about how someone used a Raspberry Pi and some maker fu to connect 0x7 on their terminal to a cathedral or something.
A guy at the office has a 3D printed contraption featuring a solenoid striking a bike bell for his terminal.. and there’s a cathedral nearby.. don’t give him ideas..
Another way to look at it is that Ctrl+G takes the code (ASCII) of G, i.e., 71 (binary 1000111) and toggles its 7th least significant bit to get 7 (binary 111) and indeed 7 is the code of the BEL character.
This explanation is over-simplified though. In practice, different systems have used different techniques to derive control codes from key chords. I have a more detailed article about this at https://susam.net/blog/control-escape-meta-tricks.html if anyone is interested to read it.
