(I should probably implement the memory part in bmo somewhere.)

Let's keep ini file names consistent with tool names.  Since bmo-uris is
gone, this is not even a shared file anyway.

Can be useul for emphasized/strong text in Markdown.

Externally stored because:

 *  vimb config could be a bit security-sensitive thing, at least until
    I find out what I want in there and how to split things properly.

 *  Same appliest to weechat, plus it has this habit of rewriting config
    on exit, which could become annoying if stored in git and changed
    frequently.

 *  Avoid icons that don't work well on Debian (conflict in Private Use
    Unicode area).

 *  Simplify battery statuses even more (with better understanding
    of ACPI statuses).

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.

Silly but for now it will suffice.  Maybe one day I'll learn the magic
of systemd so that I'll be able to set this up in a less embarrassing
way.

experimental -- finger injury risk ;)

When case is left without quotes, Vim's default syntax highlighter shows
the left bracket in strong, error-y red style (not sure why, e.g.
ShellCheck does not complain about that notation).  It seems to work
fine when quoted, though.

The / main page seems to be a bit too "dangerous", this should make it
easy to go to a particular subscribed subreddit without much
distraction.

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.