added a -l switch to scripts to only list dirs containing scripts

also made a huge time savings by checking the executable flag _before_ calling `file`
-	I can't imagine why I wasn't doing this before
-	in one test, this cuts a 3:20 run down to 25 seconds ...
better word counting for blog posts
small tweaks to blogify:

-	create a way to have preformatting (i.e. to preserve linebreaks) inside blockquotes
-	preserve double spaces after more chars
eventually I'm going to have to give up on this approach and write a real parser
-	(but not today)
some changes to `vimS` to make it easier to work with and more full-featured

can now do `vimS -e` to edit a session file
-	this is useful for session files that have vars in them
-	or to pretend like you never opened that one file
can now do `vimS -lv` to show full path names of session files
-	in case you're not sure where the session file is coming from
can now do `:SM` in vim to save a "marks file"
-	this helps get around the fact that local file marks aren't saved in a session file
-	they are saved in ~/.viminfo, but only for a certain number of files
-	if you edit more than that number of files before you come back around to your session, your marks are lost :-(
-	this way, marks are saved in a special viminfo file which is $sessionfile.marks
-	also, once you do `:SM` once, it will auto-save (and auto-reload) marks with that session forever
-	obviously this involves some cooperation between `vimS` and the ~/.exrc
fix `unbranch` alias now that `vc unbranch` works

also set up an override for unbranch on CE
new command: `imgrep`

this does the tedious task of searching through my Pidgin logs and twiddling the output to be somewhat legible
a few vagrant commands that vagrant really should have provided:

`vagrant-scp`:
-	there's no way to scp a file to your Vagrant box :-/
-	so this handles it
`vagrant-list`:
-	you can list all your Vagrant boxes,
-	and you can check the status of the current box,
-	but there's no way to check to see what instances are running in all boxes
-	to do this, you have to go past Vagrant down to the VBox level
-	so this script handles that
-	note that it's $work-specific, as our $work Vagrantfile uses an env var to determine which box to load