Mercurial > vim

comparison runtime/doc/undo.txt @ 32721:94f4a488412e v9.0.1683

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Updated runtime files Commit: https://github.com/vim/vim/commit/6efb1980336ff324e9c57a4e282530b952fca816 Author: Christian Brabandt <cb@256bit.org> Date: Thu Aug 10 05:44:25 2023 +0200 Updated runtime files This is a collection of various PRs from github that all require a minor patch number: 1) https://github.com/vim/vim/pull/12612 Do not conflate dictionary key with end of block 2) https://github.com/vim/vim/pull/12729: When saving and restoring 'undolevels', the constructs `&undolevels` and `:set undolevels` are problematic. The construct `&undolevels` reads an unpredictable value; it will be the local option value (if one has been set), or the global option value (otherwise), making it unsuitable for saving a value for later restoration. Similarly, if a local option value has been set for 'undolevels', temporarily modifying the option via `:set undolevels` changes the local value as well as the global value, requiring extra work to restore both values. Saving and restoring the option value in one step via the construct `:let &undolevels = &undolevels` appears to make no changes to the 'undolevels' option, but if a local option has been set to a different value than the global option, it has the unintended effect of changing the global 'undolevels' value to the local value. Update the documentation to explain these issues and recommend explicit use of global and local option values when saving and restoring. Update some unit tests to use `g:undolevels`. 3) https://github.com/vim/vim/pull/12702: Problem: Pip requirements files are not recognized. Solution: Add a pattern to match pip requirements files. 4) https://github.com/vim/vim/pull/12688: Add indent file and tests for ABB Rapid 5) https://github.com/vim/vim/pull/12668: Use Lua 5.1 numeric escapes in tests and add to CI Only Lua 5.2+ and LuaJIT understand hexadecimal escapes in strings. Lua 5.1 only supports decimal escapes: > A character in a string can also be specified by its numerical value > using the escape sequence \ddd, where ddd is a sequence of up to three > decimal digits. (Note that if a numerical escape is to be followed by a > digit, it must be expressed using exactly three digits.) Strings in Lua > can contain any 8-bit value, including embedded zeros, which can be > specified as '\0'. To make sure this works with Lua 5.4 and Lua 5.1 change the Vim CI to run with Lua 5.1 as well as Lua 5.4 6) https://github.com/vim/vim/pull/12631: Add hurl filetype detection 7) https://github.com/vim/vim/pull/12573: Problem: Files for haskell persistent library are not recognized Solution: Add pattern persistentmodels for haskell persistent library closes: #12612 closes: #12729 closes: #12702 closes: #12688 closes: #12668 closes: #12631 closes: #12573 Co-authored-by: lacygoill <lacygoill@lacygoill.me> Co-authored-by: Michael Henry <drmikehenry@drmikehenry.com> Co-authored-by: ObserverOfTime <chronobserver@disroot.org> Co-authored-by: KnoP-01 <knosowski@graeffrobotics.de> Co-authored-by: James McCoy <jamessan@jamessan.com> Co-authored-by: Jacob Pfeifer <jacob@pfeifer.dev> Co-authored-by: Borys Lykah <lykahb@fastmail.com>
author Christian Brabandt <cb@256bit.org>
date Thu, 10 Aug 2023 06:30:06 +0200
parents 67f31c24291b
children 4635e43f2c6f
comparison
equal deleted inserted replaced
32720:a34d49643187 32721:94f4a488412e
109 To do the opposite, use a new undo block for the next change, in Insert mode 109 To do the opposite, use a new undo block for the next change, in Insert mode
110 use CTRL-G u. This is useful if you want an insert command to be undoable in 110 use CTRL-G u. This is useful if you want an insert command to be undoable in
111 parts. E.g., for each sentence. |i_CTRL-G_u| 111 parts. E.g., for each sentence. |i_CTRL-G_u|
112 112
113 Setting the value of 'undolevels' also closes the undo block. Even when the 113 Setting the value of 'undolevels' also closes the undo block. Even when the
114 new value is equal to the old value. In |Vim9| script: > 114 new value is equal to the old value. Use `g:undolevels` to explicitly read
115 &undolevels = &undolevels 115 and write only the global value of 'undolevels'. In |Vim9| script: >
116 &g:undolevels = &g:undolevels
116 In legacy script: > 117 In legacy script: >
118 let &g:undolevels = &g:undolevels
119
120 Note that the similar-looking assignment `let &undolevels=&undolevels` does not
121 preserve the global option value of 'undolevels' in the event that the local
122 option has been set to a different value. For example: >
123 " Start with different global and local values for 'undolevels'.
124 let &g:undolevels = 1000
125 let &l:undolevels = 2000
126 " This assignment changes the global option to 2000:
117 let &undolevels = &undolevels 127 let &undolevels = &undolevels
118 128
119 ============================================================================== 129 ==============================================================================
120 4. Undo branches *undo-branches* *undo-tree* 130 4. Undo branches *undo-branches* *undo-tree*
121 131
364 374
365 *clear-undo* 375 *clear-undo*
366 When you set 'undolevels' to -1 the undo information is not immediately 376 When you set 'undolevels' to -1 the undo information is not immediately
367 cleared, this happens at the next change. To force clearing the undo 377 cleared, this happens at the next change. To force clearing the undo
368 information you can use these commands: > 378 information you can use these commands: >
369 :let old_undolevels = &undolevels 379 :let old_undolevels = &l:undolevels
370 :set undolevels=-1 380 :setlocal undolevels=-1
371 :exe "normal a \<BS>\<Esc>" 381 :exe "normal a \<BS>\<Esc>"
372 :let &undolevels = old_undolevels 382 :let &l:undolevels = old_undolevels
373 :unlet old_undolevels 383 :unlet old_undolevels
384
385 Note use of `&l:undolevels` to explicitly read the local value of 'undolevels'
386 and the use of `:setlocal` to change only the local option (which takes
387 precedence over the corresponding global option value). Saving the option value
388 via the use of `&undolevels` is unpredictable; it reads either the local value
389 (if one has been set) or the global value (otherwise). Also, if a local value
390 has been set, changing the option via `:set undolevels` will change both the
391 global and local values, requiring extra work to save and restore both values.
374 392
375 Marks for the buffer ('a to 'z) are also saved and restored, together with the 393 Marks for the buffer ('a to 'z) are also saved and restored, together with the
376 text. 394 text.
377 395
378 When all changes have been undone, the buffer is not considered to be changed. 396 When all changes have been undone, the buffer is not considered to be changed.