Mercurial > vim
changeset 33976:accd07813f71
runtime(doc): Update change.txt (#13725)
Commit: https://github.com/vim/vim/commit/955652f6df9c4a1048fde8028c5c7f7871b5f71a
Author: K.Takata <kentkt@csc.jp>
Date: Wed Dec 20 04:15:47 2023 +0900
runtime(doc): Update change.txt (https://github.com/vim/vim/issues/13725)
Fix-up and clarify commit e06f2b498ccca921f34a1bec4464f042a5a2cabd
Signed-off-by: Ken Takata <kentkt@csc.jp>
Signed-off-by: Christian Brabandt <cb@256bit.org>
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Tue, 19 Dec 2023 20:30:04 +0100 |
| parents | dcf5b936196b |
| children | eed6e54017c5 |
| files | runtime/doc/change.txt |
| diffstat | 1 files changed, 7 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/runtime/doc/change.txt +++ b/runtime/doc/change.txt @@ -1,4 +1,4 @@ -*change.txt* For Vim version 9.0. Last change: 2023 Dec 08 +*change.txt* For Vim version 9.0. Last change: 2023 Dec 19 VIM REFERENCE MANUAL by Bram Moolenaar @@ -452,9 +452,12 @@ octal number. Note that when 'nrformats' includes "octal", decimal numbers with leading zeros cause mistakes, because they can be confused with octal numbers. -Note similarly, when 'nrformats' includes "bin", binary numbers with a leading -'0b' or '0B' can be interpreted as hexadecimal rather than binary since '0b' -are valid hexadecimal digits. +Note similarly, when 'nrformats' includes both "bin" and "hex", binary numbers +with a leading '0x' or '0X' can be interpreted as hexadecimal rather than +binary since '0b' are valid hexadecimal digits. CTRL-A on "0x0b11" results in +"0x0b12", not "0x0b100". +When 'nrformats' includes "bin" and doesn't include "hex", CTRL-A on "0b11" in +"0x0b11" results in "0x0b100". When the number under the cursor is too big to fit into 32 or 64 bit (depending on how Vim was build), it will be rounded off to the nearest number