created 2001 · complexity intermediate · author slimzhao · version 5.7
This command given in :help 12.4 will reverse all lines in the current buffer:
- : start command-line mode.
- g means you'll take an action on any lines where a regular expression matches
- / begins the regular expression (could have used any valid delimiter)
- ^ matches the start of a line (which matches all lines in the buffer)
- the second / ends the regular expression; the rest is an Ex command to execute on all matched lines (i.e. all lines in buffer)
- m means move (:help :move)
- 0 is the destination line (beginning of buffer)
This takes advantage of the implementation detail noted just below :help :v, that
:g works by first marking all lines that match, then visiting each mark in order to run the command. Hence, you first move the first line to the top, then the second above the first, then the third above the second, etc.
If you do not want to reverse the entire file, you can supply the range of lines to reverse to the command and adjust the destination accordingly. For example, to reverse only lines 100-150:
If you are running Vim on a Unix-like operating system, the
tac† utility will reverse all lines for you. Like any external utility, you can call
tac from Vim as an alternate method:
A range will also work with this method:
Either of these methods can easily be assigned a mapping or Ex command.
command! -bar -range=% Reverse <line1>,<line2>g/^/m0|nohl " REVERSE line ordering, and move those lines to the top of the file.
It is probably more useful to reverse the lines in-place, i.e. without moving them to the top:
command! -bar -range=% Reverse <line1>,<line2>g/^/m<line1>-1|nohl
OK I give up. Why would you want to do this?
- 1. I'm inclined to agree with the implication lurking in your question, but sometimes style triumphs over utility and the cuteness is sufficient to justify this tip. However, I actually used the command from this the tip a month ago when I had a log of lines in order newest-first, and I needed it in the reverse order. JohnBeckett 01:24, January 8, 2010 (UTC)
- 2. I think without a range it has very few real uses, but with a range (which could even be a visual selection with
'<,'>) it becomes much more useful. With minor tweaking, using an actual pattern for the
:gcommand and a range on the
:mcommand (which could contain searches, etc.) this simple command becomes extremely versatile for moving large blocks of text and placing in reverse order. --Fritzophrenic 14:32, January 8, 2010 (UTC)
- 3. I just want to say thank you very much for this hint. I use vim to organize and search my account log (Kontobewegungen) and I receive the account info as list newest first so this hint was very helpful for me. --firstname.lastname@example.org 10:00, October 4, 2010 (UTC)
- 4. This is actually very useful if recovery fails. On a Unix system you can still recover your edits by typing "strings .swp" at a command line, but the lines are reversed. This command sets things right. 23:20, February 8, 2011 (UTC).
- 5. Another real world: I installed a ruby gem with many dependencies on the wrong system. I wanted to remove the 20+ resulting gems, but because of gem dependencies I needed to remove them in opposite order. Google got me here, and this tip worked perfectly. 01:50, July 3, 2011 (UTC)