The idea here is that periodically you do something like:
$ comment "messing with wifi settings"
$ comment "trying out new file managers"
And then you've got some human-readable context in your shell history.
This is the stub of a larger, better idea, I think.
...I've been using this more consciously of late. It's a decent way
to deliberately collapse sections of a file.
- zi enables folding
- `{{{` and `}}}` denote a section
BPB_TabDrop will open a symlinked file in its canonical location, which is
better (for example) for opening a version controlled .vimrc that is
symlinked from the user's home directory.
This particular cat is pretty thoroughly vacuumed.
Moving stuff to a home/ subdirectory turns out to have been a painful
idea, because I had symlinked to a bunch of paths that went away. This
really needs some kind of abstraction over the top of it, even if it's just
a script to manage the links.
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.
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.