This involves changing grepprg, running, and then changing it back.

Not entirely optimal, but the location window has some good features.

Changes notes-links-for output to match (ish) grep format.

So as to have longer to type longer mappings.

Unclear whether this is causing a perceptible lag in running filters, but
maybe.

This comes in Freenode #vimwiki a lot.

Also groups some autocommands.

argv.pl: Print out the arguments to a script.

bad-regex.pl: What happens when you compile a broken regex?

This is incredibly specific to my vimwiki setup at the moment.  It'll
probably expand to include other things, but I decided to just jam it into
one nice generic top-level namespace for now.

...instead of -m.

- changes various BPB_Foo functions to s:FOO, which is cleaner and does
    less trampling on the global namespace

  - adds some vimwiki log / link utilities based on an SQLite db I'm
    building elsewhere

  - comments slightly clearer about how unlikely this is to work for most
    users

  - removes some cruft, including an experimental scratch wiki

Not exactly sure when this got rehomed, but at least it looks like it's
actively maintained.

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

Renames fragment-vw-diarylink.

Short version:  You can do it, but it's kind of a bad idea, at least the
way I'm using them.

In shell and grep.  Awful.  Sort of works.  Still awful.

It probably doesn't matter what's passed in in this case.

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

This has more features than parse_git_branch, though it could use a way
to display the _number_ of untracked / modified files (I'll have to see
if that's available).

I'm not including a copy of git-prompt.sh in the repo.  If it's not
available in the user's home directory, I mock up a function that uses
the old parse_git_branch instead.

...since this isn't a thing any more.

nvim is totally horked on this system at present.