In this screencast, I teach how to record a useful vim macro that does a simple RSpec “refactoring”.
(You’ll want to open it on Youtube and watch in high-resolution.)
Commands used:
7G – jump to line 7
“td – delete into the t register
“tp – put from the t register
qq – start recording a macro (just a series of keystrokes) into register q
@q – execute the keystrokes stored in register q
vmap – set up a mapping active only when in visual mode
Last week I posted How to land your first patch in Rails.
The post was well-received, but one commenter asked if I might put together more-detailed steps on how to make your first docpatch. Well, I’ve done just that, and the result is the screencast below.
It’s only 4 minutes, but contains everything you need to know to get your name on the Rails Contributors list. Check it out!
Update: in the screencast, I mention that you need to message lifo for commit access to docrails. However, as Xavier noted below, docrails now has public write access for everyone, so need to perform that step.
By the way, if you liked the video, you should check out my other screencasts for Rails programmers.
Today I learned that you can pass a block to Class.new, like so:
This is a handy for creating one-off classes; the kind you’ll throw away quickly.
It’s likely that you’d do this during tests. Here’s a test in active_support that uses this technique:
Another thing I picked up at the same time: you can pass a constant to Class.new and it will set that as the superclass:
Here’s another test from Rails. This one makes use of both tricks I just showed you: