After reading:

https://post.lurk.org/@fragmentscenario/105901885046776610

...which it sometimes may not, if not properly mounted or whatever.

Gives an interface for controlling multiple audio channels / sinks.

- Uses LWP::Simple instead of shelling out to curl
  - Prints a one-line tab-separated thing for each post
  - Adds Getopt::Long and some usage info

https://mspsocial.net/@earthtopus/105059383725674327

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.

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.

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

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

Renames fragment-vw-diarylink.

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

Finally stopped working - the Boulder Valley School District "improved"
its site.  It was a pretty good run, all things considered.

I keep forgetting to use this.