I'm not sure these are really the right names, but the idea is that you
have some file you want to move, but you aren't real keen on typing out
a full destination path right now.  So you do something like:

    yank file_to_move_later
    # other stuff
    cd some_destination_directory
    unyank

The implementation should really be more general.  It would be cool if you
could stack files.  It _might_ be cool if it made hardlinks, for various
reasons, but I also suspect that complicates things.

Maybe these should be called `delete` and `put`?  Maybe the `unyank`
should copy rather than moving the file?  It feels like mostly that
isn't what I want, for various reasons.

Might get rid of this eventually, but it makes long, unwrapped Markdown
files more palatable.

There's probably a better way to do this, but right now it just adds a
chpwd func to .zshrc to tack dirs onto ~/.directory_history.  The h alias
now uses this file instead of the dirs builtin.

This is dumb.

For some reason a bright background seemed helpful the other day.

`main()` now takes 5 explicit args - this is at least 2 too many, so should
probably be refactored.

`--source` strikes me as a little clearer than `--target`.

`-x` and `-y` can be used to set a thumbnail size.

Fromt this brief experience, docopt seems really nice.

I went back to a lower-res monitor.  It's great.

scratch:  top half
notes:  right half

A little wmctrl wrapper.  Required adding EWMH stuff to xmonad for this
to work properly.

Re: ultisnips:

  https://p1k3.com/2016/4/14/

Re: Vundle:

  http://www.gmarik.info/blog/2014/why-i-stopped-contributing-to-vundle/

This is a more general, unformatted raw output version of vim-filter-exec.
It will be useful for pulling some utility output into HTML / Markdown
docs in a more generalized way.

I'm using it to make simple image galleries with the terrible python
script in bin/html-gallery.

I don't know if I'll stick with vim-airline for my statusbar, but it has
some appealing features.

Dropped terminal fonts down a bit in size.  Seems better to have a
little more context for editing on this display.  At this res, with
those fonts, I get a 147x40 terminal.  It's reasonably legible.

(I'm currently on a System76 Galago UltraPro or whatever it's called,
purchased in August of 2014 or thereabouts.)

For some Python or something?  I dunno.  It didn't work anyway.

Via bishop at:

http://stackoverflow.com/questions/263890/how-do-i-find-the-width-height-of-a-terminal-window

Getting old may beat the alternatives, but it sure is kind of shit on its
own terms in a lot of ways.

everything is so tiny my god i am old

https://github.com/thcipriani/dotfiles/blob/master/xmonad/xmonad.hs
https://pbrisbin.com/posts/xmonad_scratchpad/
http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Util-NamedScratchpad.html
https://pinboard.in/u:brennen/t:xmonad/

...by removing a doFloat.  Things seem normal, minus this, since
(evidently) dialogs are floated by default.  I was getting this horrible
flickering effect before.  In my mind, I added this in the first place
to try to solve that problem, but obviously something has changed.