The sack of sand that broke the camel's back:

    https://github.com/privacytoolsIO/privacytools.io/issues/740#issuecomment-460076395

Finally stop: painstakingly changing it manually for every new workspace
ever.

(...for no reason; just something in my brain preventing me to add
this line for ~4 years.)

This will come handy as I have my first Bluetooth device now.

It's still a great client, it's just that I don't have anybody to talk
to on Jabber anymore, and since I've forgotten jabber.cz password and
it's really PITA to restore it, it's a bit annoying to have to cancel
the dialog all the time.

I'm giving up trying to make X load this file properly on boot.

This will make it easier to control appearance per host, as we already
have setup for per-host XRDB resources.

Mostly useful for important projects...

Does not work with every color scheme.

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

Because changing desktop background via shortcut is badass.  (And using
PrintScreen for that is even clever.)

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?

Can be useul for emphasized/strong text in Markdown.

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'.

Use systemd service units where applicable, elsewhere use stman (in
host-specific branch).

Psi was basically perfect, but it turns out that with Jabbim.cz, we'll
just need client-side spam filter.

experimental -- finger injury risk ;)

The in-line comment startles i3, and by the way using bindsym here is
not so useful when using only CS and EN, which have 'n' at the same
place.

... instead of crawling through hoops.

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.

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