Mercurial > vim
diff runtime/doc/options.txt @ 20613:9edb439adbea v8.2.0860
patch 8.2.0860: cannot use CTRL-A and CTRL-X on unsigned numbers
Commit: https://github.com/vim/vim/commit/aaad995f8384a77a64efba6846c9c4ac99de0953
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun May 31 15:08:59 2020 +0200
patch 8.2.0860: cannot use CTRL-A and CTRL-X on unsigned numbers
Problem: Cannot use CTRL-A and CTRL-X on unsigned numbers.
Solution: Add "unsigned" to 'nrformats'. (Naruhiko Nishino, closes https://github.com/vim/vim/issues/6144)
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Sun, 31 May 2020 15:15:04 +0200 |
| parents | 501b72481d0a |
| children | d6827bd31d1d |
line wrap: on
line diff
--- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -5427,6 +5427,15 @@ A jump table for the options with a shor bin If included, numbers starting with "0b" or "0B" will be considered to be binary. Example: Using CTRL-X on "0b1000" subtracts one, resulting in "0b0111". + unsigned If included, numbers are recognized as unsigned. Thus a + leading dash or negative sign won't be considered as part of + the number. Examples: + Using CTRL-X on "2020" in "9-2020" results in "9-2019" + (without "unsigned" it would become "9-2021"). + Using CTRL-A on "2020" in "9-2020" results in "9-2021" + (without "unsigned" it would become "9-2019"). + Using CTRL-X on "0" or "18446744073709551615" (2^64) has + no effect, overflow is prevented. Numbers which simply begin with a digit in the range 1-9 are always considered decimal. This also happens for numbers that are not recognized as octal or hex.