Macos – How to trigger a notification from a remote terminal in OS X

emacsiterm2macosnotificationsterminal

I am running a long process on a remote shell. I would like to trigger a notification when the process is complete. This answer does not suffice, because the long command is on a remote server, so it cannot call terminal-notifier.

I can get close to my desired outcome by using an iTerm2 trigger. For example if I run the following on the remote server and set up an iTerm2 trigger for __FINISHED__:

./long_process && echo "\__FINISHED__"

This has the undesirable feature that every time I scroll back to this command in my editor or my code (I'm running code in an emacs shell), the notification triggers.

One solution might be some kind of text notification that iTerm2 will recognize, but that will not appear in an emacs scrollback buffer.

Best Answer

You have not specified what kind of notification you want nor what OS the remote server is running so I am going to have to make some assumptions here. I will assume you don't really care what type of notification it is as long as you are notified and that the remote server is running some flavor of *nix.

Send yourself an email. If sendmail is configured on the server, you could do
```
./long_process && echo "Job done" | sendmail pnj@yourdomain.com
```
ssh back to your local machine (assuming this is possible) and make it talk to you. See here for more cool ways of making OSX beep at you.
```
./long_process && ssh you@local.ip say "Yo! All done"
```
or
```
./long_process && ssh you@local.ip terminal-notifier -message "Job finished!" -title "Info"
```
If you are connecting from a dynamic IP and you have configured your router so that you can ssh to that dynamic IP, you can do this (assuming you are only currently connected from your remote machine):
```
ip=$(who | grep $USER | perl -lne 's/\$(.+?)\$\s*$//; print "$1"' | tail -n 1) &&
 ./long_process && ssh you@$ip terminal-notifier -message "Job finished!" -title "Info"
```
You can set up password-less ssh in the normal way. It should not be affected by the dynamic IP. Once you have done so, the code above will work.
Use pushover and send a notification to your Android or iOS device (if you have one)
```
./long_process && pushover.pl "All done"
```

Related Solutions

Linux – Grep exits abnormally with code 123 when running rgrep on emacs

Looking at xargs exit code documentation:

123 if any invocation of the command exited with status 1-125

but according to grep documentation 1 is the exit status if grep didn't match the pattern

EXIT STATUS
   Normally, the exit status is 0 if selected lines are found and 1 otherwise.

So to me it seems that the command line that emacs uses to issue an 'rgrep' search will always return 123, and this error either needs to be suppressed or replaced with a command line such as

find . -type f \( -name \*.\[ch\] \) -exec grep -i -nH -e v4l

Macos – How to prevent emacs from loading `update_terminal_cwd` with autojump

I know this topic is old, but I had the same issue and found no solution (and this page is the first google result). Here is my fix (might not be the best, but works):

if [ `(type update_terminal_cwd | grep -q 'shell function' | wc -l) 2> /dev/null` -eq 0 ]; then
    update_terminal_cwd() {
        return
    }
fi

[[ -s `brew --prefix`/etc/autojump.sh ]] && . `brew --prefix`/etc/autojump.sh

Regards,

Best Answer

Related Solutions

Linux – Grep exits abnormally with code 123 when running rgrep on emacs

Macos – How to prevent emacs from loading `update_terminal_cwd` with autojump

Related Question