iterm2 support

[mooreniemi]

see also: #80

terminal-notifier -title "RSPEC" -message "⚑ Tests done."

Works in the terminal directly, but if I use "Run command..." in iTerm2 triggers, it doesn't work. I confirmed the trigger was firing correctly (used text highlight to check).

I'm on Yosemite 10.10.5.

[julienXX]

I'm not an iTerm user so I won't be able to help here. Sorry.

[mooreniemi]

@julienXX any other collaborators available? if not, feel free to just close this and i'll assume it'll remain unsupported. (i could try to take a look myself but this is a bit outside my wheelhouse :))

[julienXX]

I'll leave it opened in case someone has an answer.

[semikolon]

Did you try referencing the binary with the exact path? /usr/local/bin/terminal-notifier or such?

[shigemk2]

Me neither. My environments are

• Mac OSX Yosemite
• iTerm2 2.1.4
• terminal-notifier's path is /usr/local/bin/terminal-notifier

When executing sample command in README, command freezes and I didn't have any results.

$ echo 'Piped Message Data!' | terminal-notifier -message 'Check your Apple stock!'
// Freezing...

[msaspence]

I tried referencing the exact path and sent the exit code to a txt file and get 127

[dnakagome]

+1 for @semikolon

Giving the exact path in "Parameters" for "Run Command..." triggers terminal-notifier perfectly.

I'm using El Capitan though.

My environments are:

• OS X El Capitan 10.11.2
• iTerm2 2.1.4
• terminal-notifier 1.6.3

[guidoschmidt]

Try using the ruby gem - works for me using iTerm2 on OS X 10.11.3

[ssbarnea]

You can close the bug, I tested and echo "msg" | terminal-notifier works perfectly.

Also, for your information iTerm3 has a trigger named Post Notification, which does this without even needing this wrapper.

[ciudilo]

@ssbarnea does not work in iTerm2 on OS X 10.11.4

[theoretick]

I too am having issues with this. I wanted more granularity then Post Notification provides so I've tested with terminal-notifier and osx-notifier without success. Not sure what the issue is, but I have successfully used apple script:
osascript -e 'display notification "Tests Passed" with title "Terminal"'.

As you can see from my example what I'd really like is to trigger a different icon (reporting app? i'm unfamiliar with how notifications work) so I can easily see a success/failure. With osx-notifier I would do something like:
osx-notifer --type=pass --message="Specs Passed"
or
osx-notifer --type=fail --message="Specs Failed: \1 failures" (with trigger capture groups).

[williscool]

@ciudilo @theoretick

thanks to @semikolon

I figured it out.

You have to use the full path to the executable in the "Run Command" trigger

i.e.

/usr/local/bin/terminal-notifier -title 'Notification Title' -subtitle 'Server Ready'

[julienXX]

Closing the issue, feel free to re-open if needed.