Doing more with each change

A session at Vim London July

In test-driven development, we aim to follow the red, green, refactor cycle. That is: write a failing test (red), make it pass (green), then make it good (refactor). In A Refactoring Workout: Relentlessly Green, Katrina Owen describes two rules for refactoring under green:

  • Run the test after every single change
  • If the test fails, it should take exactly one undo to get back to green

That means that "the size of a step is limited by what your editor can revert with a single undo."

I'd like to talk about a few patterns of Vim usage that let you do more with each change. Some of these techniques use core functionality, while others will use plugins such as surround, UltiSnips, and exchange. I'd like to finish with a discussion, inviting the audience to suggest more tips and plugins in a similar vein.

About the speaker

This person is speaking at this event.
Drew Neil

The voice of @vimcasts. Author of https://pragprog.com/book/dnvim2/practical-vim-second-edition bio from Twitter

Coverage of this session

Sign in to add slides, notes or videos to this session

Tell your friends!


Date Tue 29th July 2014

Short URL


Official event site


View the schedule



Books by speaker

  • Practical Vim

See something wrong?

Report an issue with this session