Uses date(1) to parse a given date and use it for the header (by way of
bin/today) instead of just defaulting to current date.
This way the template is accurate when opening other diary dates from
the calendar.
It looks like I went to check whether commandlog was installed a while
back and neglected to actually specify "commandlog" instead of the "foobar"
from the example I was looking at, so commandlog hasn't been running for a
couple of months.
I'm not even currently using this file, really, but it's a partial list
of dependencies so will be helpful to have for better automating installs
later on.
Uses tabbedBottom instead of tabbed in layout.
I'm not totally sold on this - it maybe doesn't _look_ as cool - but I
think it makes the tabs more noticeable.
Using `moveTo Prev HiddenWS` and `moveTo Next HiddenWS` instead of `prevWS`
/ `nextWS` gets rid of a behavior where cycling workspaces with the arrow
keys will cause workspaces to swap between screens, which has always been
slightly confusing. If a workspace is already displaying, I'm probably
not looking for it.
It turns out that you can use `:0r !foo` to avoid the blank line I was
deleting in BPB_DiaryFragement() and BPB_DatestampHTML().
Also remove a commented-out YouCompleteMe install.
- switch to iceberg color scheme
- switch airline theme to luna for console vim
- add dockerfile, go, and yaml syntax highlight to vimwiki code blocks
- populate completion from dictionary, set dictionary to
/usr/share/dict/words and (experimentally) an index of vimwiki files
- only generate p1k3 templates on lower-case file matches
The `--no-sort` option to fzf effectively gives more recent matches first,
which turns out to be what I want in almost every case.
You can now do `h foo` and foo will be populated as the query, which feels
a bit more natural at times.
The answer by Gilles was the hint I needed here:
"Leaving the default value of xterm and setting the termName resource to
xterm-256color (which causes the environment variable TERM to be set to
the same value) are thus both sensible choices. Setting TERM to arbitrary
values wouldn't work, but both xterm and xterm-256color make sense."
https://unix.stackexchange.com/questions/108410/is-it-correct-to-set-the-term-variable-manually