Re-run [re-edited] sequence of commands in vim history

In vim: q: && v[cursor movement]y && [paste/edit/save to /tmp/tmp.vim] && move to window to modify && :so /tmp/tmp.vim
It's actually really helpful if you've done a lot of replaces in say a header file, and now you want to replace the same text in the source code file.

0
By: tmsh
2010-05-12 03:03:40

What Others Think

You'd be better investigating :bufdo (execute commands in all buffers). e.g. vim myfile.[ch] And in vim: :bufdo %s/old_function/new_function/ge The /ge means: 'g' (global: all matches in a line) and 'e' suppress error message if there are no matches.
flatcap · 427 weeks and 2 days ago
Awesome, thanks. Hadn't thought of that..
tmsh · 427 weeks ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: