Vim Redo Command: Ctrl+R, :redo, and Undo History Navigation

vim redo is the operation of reversing an undo in the Vim text editor, executed via Ctrl+r in Normal mode or the :redo Ex command. It restores the most recently undone change.

# Normal mode
Ctrl+r          # Redo one change
{count}Ctrl+r   # Redo count changes (e.g., 5Ctrl+r)

# Command-line mode
:redo           # Redo one change (same as Ctrl+r)
:later [N]      # Redo N changes (time- or count-based)
:later [N]s     # Redo N seconds forward in undo history
:later [N]m     # Redo N minutes forward
:later [N]h     # Redo N hours forward
:later [N]d     # Redo N days forward

Vim keeps a full history of every change during a session, including after saves. Redo operates on the linear undo stack; for branched history, use g- and g+.

Options and Flags

Usage Examples

Baseline undo/redo in Normal mode

# Insert "hello" then undo it twice, redo once
ihello
Esc
u        # Undo insertion of "hello"
u        # Undo blank (no prior change, so nothing)
Ctrl+r   # Redo the insertion of "hello" (one change)

Context: After accidentally undoing too far, Ctrl+r restores the most recently undone change. Requires the buffer to have an undo history; otherwise, E22: No undo history appears.

Redo a specific number of changes

# Make three edits, undo two, redo only the first undone edit
iedit1
Esc
iedit2
Esc
iedit3
Esc
uu       # Undo edit3 and edit2
3Ctrl+r  # Redo three changes (edit2 and edit3, but only two exist → redo both)

Context: A count prefix jumps multiple steps without repeated keystrokes. If the count exceeds available redo steps, Vim redoes all remaining undone changes.

Time‑based redo with :later

# Make changes over 2 minutes, then jump back 30 seconds
:earlier 2m    # Undo changes made in the last 2 minutes
:later 30s     # Redo forward 30 seconds, restoring intermediate state

Context: The :later command accepts time suffixes (s, m, h, d) to navigate forward by a duration. This is useful for correcting an over-undo by a known time interval.

Troubleshooting & Common Errors

Performance Considerations

Undo history size and disk persistence affect redo latency. Tune these settings in .vimrc to balance memory and speed:

• undolevels — maximum number of saved changes. Default 1000; set :set undolevels=5000 (watch memory). Use -1 for unlimited (risky on huge files).
• undoreload — saves undo information when reloading a file. Default 0 (off). Enable with :set undoreload=10000 to keep a change window across reloads.
• undofile / undodir — persistent undo files. Disable on network filesystems with :set noundofile to avoid latency.

Check current settings:

:set undolevels?
:set undoreload?
:set undodir?

Frequently Asked Questions

" undo then switch branch
u         " undo one change
g-        " go to older state on alternate branch
g+        " redo forward along the alternate branch