Re:Using iTerm2 with Growl for Notifications
by syncerr on Sunday July 14, 2013 @11:12PM
(#6043476)
When using terminal-notifier, use the -group ID and -remove ID together -- otherwise, the swipe-to-notification-area gets cluttered. Alternatively, do a sleep and close it automatically.
Re:Using iTerm2 with Growl for Notifications
by syncerr on Sunday July 14, 2013 @11:08PM
(#6043465)
There is an automatic way of doing this is OSX[1]. You may also want to use terminal-notifier instead of growl[2]. My experience was that the bash prompt became too slow. However, results seem to vary.
Re:Using iTerm2 with Growl for Notifications
by smm2000 on Sunday July 14, 2013 @11:28PM
(#6043526)
Good thing about bash script is that it works when you compile on remote Linux machine. terminal-notifier works only if you development is completely on Mac.
Re:Using iTerm2 with Growl for Notifications
by nfoz on Monday July 15, 2013 @01:10AM
(#6043815)
Popup notifications are a horrible idea, and they're a horrible idea in every OS in which they're implemented.
Especially so in MacOS X where there's already dedicated space where notificiations could choose to appear, rather than popping up. I think Growl should see if it can incorporate itself into the top-bar instead.
Re:Using iTerm2 with Growl for Notifications
by tazjin on Monday July 15, 2013 @01:56AM
(#6043955)
Growl is integrated into OS X's notification center (which provides popup notifications).
I would actually like to have the old Growl back (Notification Center is completely disabled on most of my machines because I find it horribly annoying, whenever I open it it's full of months old notifications because it does not have a proper "read item"-mechanism. In addition to that once you unload it you will never see the OS X Update notification (Oh how I hate it) ever again.)
Re:Using iTerm2 with Growl for Notifications
by valbaca on Monday July 15, 2013 @03:16AM
(#6044159)
You can also have iTerm take actions (like ringing a bell) when it finds a match for a regular expression (like username@ in your shell prompt). The advantage here is that you can be alerted even if you're ssh'd into another machine. No growl needed.
Re:Using iTerm2 with Growl for Notifications
by smm2000 on Monday July 15, 2013 @04:01AM
(#6044264)
Provided script also works ssh'd into another machine. Main downside of using iTerm match is that it fires up when you scroll up/down or just do cat and that string is present. Annoying.
Re:Using iTerm2 with Growl for Notifications
by marceldegraaf on Monday July 15, 2013 @02:16AM
(#6044002)
You should check out the various available voices, selectable with the "-v" switch. While you're at it, let it sing In The Hall Of The Mountain King for you:
say -v Cellos Dum dum dum dum dum dum dum he he he ho ho ho fa lah lah lah lah lah lah fa lah full hoo hoo hoo
____
[1] http://tech.superhappykittymeow.com/?p=332
[2] https://github.com/alloy/terminal-notifier
Especially so in MacOS X where there's already dedicated space where notificiations could choose to appear, rather than popping up. I think Growl should see if it can incorporate itself into the top-bar instead.
I would actually like to have the old Growl back (Notification Center is completely disabled on most of my machines because I find it horribly annoying, whenever I open it it's full of months old notifications because it does not have a proper "read item"-mechanism. In addition to that once you unload it you will never see the OS X Update notification (Oh how I hate it) ever again.)
It seems so much less complex.
For now, I use "say boom" to get notified of command completions. The boom sound is funny when coupled with errors. ;-)
Thanks for the laugh!