This just wraps the older calendar(1) invocation for the moment, just
adding a layer of indirection so it can include other data.

The calendar one will get the entry syntax-highlighted correctly (it seems
to pick a syntax based on the last string).

The log one will work from any directory.

Namely log grepping for the more-atomic logs I'm experimenting with and
a calendar lookup fragment.

Renames fragment-vw-diarylink.

- commentary
  - some stuff for "log" entries in vimwiki

Adds a menu for grabbing input from bin/fragment-*.  Adds a couple of
new fragments, and moves today → fragment-today.

This needs work:

  - it's remarkably slow
  - it has an external dependency in FZF
  - I'm not sure about the keybindings
  - it removes a couple of bindings I'm really used to
  - it's not documented with "CUSTOMIZE" markers
  - this only works in gvim with a recent build of vim 8.1

It might be better if the fuzzy-finder were vim-native, if it
distinguished between full-on document templates and small fragments, etc.

I'm also starting to think it'd be good to compartmentalize some of this
config.

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