I'm currently running mcabber as my Jabber client (which uses ncurses) in a tmux session on my homeserver. Locally i run iTerm2 as a terminal emulator, which supports the triggering of growl notifications through character escape sequences
echo "\e]9;foobar\007" makes iTerm2 send a Growl message with the text "foobar".
However, when in a tmux session, the escape sequences get eaten up. Therefore using the proprietary character escape sequence \Ptmux can be used like this:
echo "\ePtmux;\e\e]9;foobar\007\e\\" to trigger a growl message from within a tmux session.
However, when I use this in my mcabber event script that gets fired when a new message is received, no notification is triggerd, as if the echo is send to the wrong terminal.
I suppose this has to do with that mcabber which triggers the script is a ncurses application so the output from my normal bash script gets lost and iTerm 2 does never see it.
I also tried calling smcup without success before echoing accoring to some ideas I discovered
tput smcup echo "\ePtmux;\e\e]9;$FROM: $MSG\007\e\\" tput rmcup
I suppose this does not work as the issue is not switching back to the "real terminal window", but more directing the output at the ncurses window.
Any ideas on this one?