From 9121f140822bb5b963061e3830a0c8673b78ab17 Mon Sep 17 00:00:00 2001 From: Marco Hinz Date: Mon, 23 Apr 2018 14:57:18 +0200 Subject: [PATCH] Fix internal persistent undo link Closes #130 --- README.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 9354e15..d50cff5 100644 --- a/README.md +++ b/README.md @@ -884,10 +884,8 @@ on. Thus, `g-` and `g+` simply go back and forth in time, respectively. | `[count]g-`, `:earlier [count]?` | Go to older text state [count] times. The "?" can be either "s", "m", "h", "d", or "f". E.g. `:earlier 2d` goes to the text state from 2 days ago. `:earlier 1f` will go to the state of the latest file save. | | `[count]g+`, `:later [count]?` | Same as above, but other direction. | -The undo tree is kept in memory and will be lost when Vim quits. See [Handling -backup, swap, undo, and viminfo -files](#handling-backup-swap-undo-and-viminfo-files) for how to enable -persistent undo. +The undo tree is kept in memory and will be lost when Vim quits. See [Undo +files](#undo-files) for how to enable persistent undo. If you're confused by the undo tree, [undotree](https://github.com/mbbill/undotree) does a great job at visualizing @@ -2179,7 +2177,7 @@ set complete-=t " disable searching tags ## Cosmetic changes to colorschemes -Always use a dark gray statusline, no matter which colorscheme is chosen: +Always use a dark gray statusline, no matter what colorscheme is chosen: ```vim autocmd ColorScheme * highlight StatusLine ctermbg=darkgray cterm=NONE guibg=darkgray gui=NONE