Daniel Schep

@zamber hmm yeah, I should make the `ntfy done --background-only` and `ntfy shell-integration --foreground-too` options configurable via the config file. @nmaggioni yup.

Welp. seems Gnome terminal no longer sets WINDOWID either. gonna play with the xdotool solution.

Doh. per my previous comment xdotool doesn't work. Not sure how to do this :cry:

Potential fix for getting the terminals WINDOWID ``` wmctrl -lp | grep $PPID # but in python and recursively since ntfy/python's ppid is bash ``` still not great bc gnome-terminal...

Right. but isn't `xdotool getactivewindow` the equivalent of `xprop -root '\t$0' _NET_ACTIVE_WINDOW`? Ie: it gets the current active window. `WINDOWID` is window ID of the terminal that ntfy is running...

Hmm.. That's a bummer. I'll have to fire up a windows VM sometime if I have time to debug it.

Very odd. I could see tmux messing up the shell integration since it has focus detection support and iTerm2 uses tmux under the hood IIRC. However, there's no reason AFAICT...

In both the plain shell & in tmux can you give me the output of: `which ntfy` and `echo $PATH`

What's your config / how are you invoking it? That error looks ntfy is trying the linux backend, telegram shouldn't need that environment variable (tho maybe that's [telegram-send](https://github.com/rahiel/telegram-send) uses does....

Potential pitfall: http://stackoverflow.com/questions/18421757/live-output-from-subprocess-command/18423003#18423003 Potential solution: http://stackoverflow.com/questions/25750468/displaying-subprocess-output-to-stdout-and-redirecting-it/25755038#25755038