github/vim-galore
1
0
Fork 0
mirror of https://github.com/mhinz/vim-galore.git synced 2025-02-23 17:49:28 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix internal persistent undo link

Browse Source 
Closes #130
This commit is contained in:
Marco Hinz 2018-04-23 14:57:18 +02:00
parent a605d459e7
commit 9121f14082
No known key found for this signature in database
GPG Key ID: 1C980A1B657B4A4F
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -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