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.

Hardly needed to do repeatedly and when it is, it's best linked with
an observed command on the same line.

... instead of crawling through hoops.

Helpful to fight cron-related issues.

Separate declaration from initialization and add variable comments.

I don't understand how could I not have it there for so long.

We want to choose browsrt with bmo-sensible now, so sensible.ini holds
this and many more similar lists.

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.

I keeo forgetting to say "modify" and even `m` alias did not help.  This
maybe...

...yep, we're getting a bit naggy...

This likely breaks hostname setting when accessing via SSH, but:

 *  it's first version that is at least somehow readable,

 *  and also WE *MAY* have fixed the long-standing PITA escaping
    errors that we used to get in urxvt if BASH_COMMAND had backslashes
    in it!

 *  Remove excess comments and optional syntax (eg. EOL `;`),

 *  use non-conflict function names,

 *  simplify PS1 generation,

 *  close PROMPT_COMMAND setup into function,

This used to be re-set in host-specific bashrc, but we already rely on
so many things installed anyway...