aboutsummaryrefslogtreecommitdiff
path: root/runtime
diff options
context:
space:
mode:
authordundargoc <gocdundar@gmail.com>2023-12-15 22:43:05 +0100
committerChristian Clason <c.clason@uni-graz.at>2023-12-16 10:29:50 +0100
commit7cae94e91e495c6ffbd32c8e9ba7d3c572610409 (patch)
tree0c7f0e5276aaa83a752a6a3a34eefc7531f9d825 /runtime
parentf4f7e294695abe7837af62b68564114de7abd0b4 (diff)
downloadrneovim-7cae94e91e495c6ffbd32c8e9ba7d3c572610409.tar.gz
rneovim-7cae94e91e495c6ffbd32c8e9ba7d3c572610409.tar.bz2
rneovim-7cae94e91e495c6ffbd32c8e9ba7d3c572610409.zip
vim-patch:e06f2b498ccc
runtime(doc): fix typo in change.txt https://github.com/vim/vim/commit/e06f2b498ccca921f34a1bec4464f042a5a2cabd Co-authored-by: Christian Brabandt <cb@256bit.org>
Diffstat (limited to 'runtime')
-rw-r--r--runtime/doc/change.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/runtime/doc/change.txt b/runtime/doc/change.txt
index fe796422c2..61e7c0c6e0 100644
--- a/runtime/doc/change.txt
+++ b/runtime/doc/change.txt
@@ -425,7 +425,7 @@ 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
-'0x' or '0X' can be interpreted as hexadecimal rather than binary since '0b'
+'0b' or '0B' can be interpreted as hexadecimal rather than binary since '0b'
are valid hexadecimal digits.
When the number under the cursor is too big to fit into 64 bits, it will be