さよなら 絶望先生

I deleted my Facebook account today.

I hardly use the thing anymore and I was starting to resent my friends for spamming me through it.

If you need to contact me - use my email. Or phone me. Or visit me in meatspace.

In other news - vipy apparently has a bug.

My last post wasn’t very clear - or actually - it was barely a post at all.

vipy is an extension to vim so that you can run your nosetests from within vim. It’ll try to find your test methods or functions if possible, or will fall back to just running your test module.

If you happen to have nose-growl/py-growl installed or nose-django installed, it’ll handle those properly too. So you get pretty notifications via Growl on OSX and you get nice Django integration.

Yay.

If you’re using the nose-django plugin, that particular nose plugin will try to hunt down your settings.py module at the current working directory, and if it’s not there - it’ll try to hunt it down by traversing up the directory path. Probably not secure, but hey - if you’ve got a better idea that doesn’t involve more configuration - I’m all ears.

Bugs:

I’ve inherited the test class naming convention from py.test in vipy so it won’t detect test classes unless they start with “Test”. This causes grief for drproject which uses plain jane class names like “TicketModelTestCase”.

I’ll have to fix that bug - thanks to Jeff Balogh for finding that bug.

Keys you’ll use:

vipy has only 2 key bindings:

<LocalLeader>tt (TestThis)
TestThis will test the current test method or function

<LocalLeader>tm (TestModule)

Run tests in the whole file.

For people who haven’t used LocalLeader in vim yet, this generally means hitting : “\tt” or “\tm” to run the tests. 3 keystrokes.

If you want, you can remap LocalLeader in vim by sticking this into your .vimrc to remap to “comma” which is what I do.

let maplocalleader = “,”

..and no - I won’t translate the title for you.