My solution is usually as follows:
$ long-running-command; open song.mp331–40 of 51 posts
My solution is usually as follows:
$ long-running-command; open song.mp3Running it on DEBUG so it covers all commands is an interesting idea. I'm not sure I'd want alerts on things like exiting vim/less though. I don't suppose there's some nifty heuristic for whether programs accept user input?
[0] [link redacted]
OP is on Mac, which has the open command, which will open its arguments the same way they'd be opened by the Finder. My solution is usually as follows: $ long-running-command; open song.mp3
I use `noti` for this: `some_task && noti` `noti some_task` both work. https://github.com/variadico/noti
You can also use noti to watch a process id, in case you start a process but forget to append noti
OP is on Mac, which has the open command, which will open its arguments the same way they'd be opened by the Finder. My solution is usually as follows: $ long-running-command; open song.mp3
Personally I have a flask app deployed on heroku that posts a message to a Discord webhook just by visiting an url. So in my case when I use ssh to run long tasks I have at the end "curl https:// .herokuapp.com/?Finished" and as soon as that commands is executed I receive a message either at my phone or computer (through a channel in a personal discord server). Probably is a bit of a 'hacky' way, and using different…
Personally I have a flask app deployed on heroku that posts a message to a Discord webhook just by visiting an url. So in my case when I use ssh to run long tasks I have at the end "curl https:// .herokuapp.com/?Finished" and as soon as that commands is executed I receive a message either at my phone or computer (through a channel in a personal discord server). Probably is a bit of a 'hacky' way, and using different…
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=795774
VTE Patch: https://src.fedoraproject.org/rpms/vte291/raw/623150318ddb9a...
gnome-terminal Patch: https://src.fedoraproject.org/rpms/gnome-terminal/raw/bb5f88...