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

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

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.

Goodbye mocp :'), hello clementine... :)

Albeit a bit hidden, Orage does have a setting to start minimized, so
it's not necessary to toggle it after start.

Thunar for easy lazy access to files (eg. videos), and gxkill which is a
tiny wrapper around xkill -- to "close" any window.

Keep it together with the quick-open $mod+Home

IOW save me some broken fingers...

...planning to re-use it for saturnin-xuris -c (like b and Shift+b but
with interactive handler choice).

Just single level for now...

Far too often I miss the grave and hit Escape; Tab is safer and also
more intuitive, should one remember the ancient windoze times...

Turns out adding new bar causes weird behavior at least on hugo; will
need to investigate and possibly file bug against i3* (unless I'm doing
something wrong).