Note that the bar is disabled by default; you will need to enable it
on-demand somwhow. One possible way is wrapping clementine in a script
like this:
i3-msg bar mode dock clementine
/usr/bin/clementine
i3-msg bar mode invisible clementine
However, due to i3 limitation, this will not guarrantee that the main
bar will always end up in the very bottom of the screen. To work around
this:
i3-msg bar mode dock clementine
sleep 1
i3-msg bar mode invisible main
sleep 1
i3-msg bar mode dock main
/usr/bin/clementine
i3-msg bar mode invisible clementine
Or vote for i3 feature request to make this more predictable:
https://github.com/i3/i3/issues/2797
Despite using this combination for several years, my brain seems to
think they are in opposite formation.
What could *possibly* go wrong if I switch them?
Basically
1. I like the verb more ("bmo, wish ..."),
2. it removes potential tab-friendliness conflict with another
sub-command I'm fancying,
3. last, but not least, the obvious alias won't have to be 'bj'.
This will ensure nagging is predictable during session: on first
opportunity (which is normally new terminal window) `tasknag` will nag
about everything, then according to preset intervals.
Use the newer, smarter, xclose rather than the crude gxkill
xclose just closes window instead of killing its owner, which would tear
down all this owner's windows along.
Uses different utilities with a different set of drawbacks, though:
* wmctrl(1) needs to be installed.
* [slop][1] can be optionally installed from source but can be unreliable
when selecting some windows, e.g. urxvt.
* If slop is missing, xwininfo is used, which, unlike xkill(1), has no
way of cancelling the user action (r-click selects a window just the
same as l-click). We work around it using timeout(1), which is
rather inconvenient, though.
But all in all, we're still better off than with xkill(1).
[1]: https://github.com/naelstrof/slop
Sorry, but $mod+BackSpace is too close to Alt+BackSpace
... which means "delete last word" in Bashese/Emacese so I often press
it several times in succession,
Although I should not tolerate own typos, I'm also really getting tired
of accidentally tearing down random windows. Sorry, this is just too
destructive.
Remove 'n' keybindings for keyboard switching (keep code-57)
Code 57 normally means N, so this layout started (rightfully, I admit)
generating conflict errors. Assigning key is probably more reliable,
though, so we'll keeo that one.
Apparently with some distros, raching 0 will turn off the display
completely. Step of 49 makes it easy to avoid that while still keeping
the advantage of huge step.