[vim/vim] A couple of corrections to the docs (Issue #18955)

lkintact

unread,

Dec 17, 2025, 2:38:27 PM (12 hours ago) Dec 17

to vim/vim, Subscribed

lkintact created an issue (vim/vim#18955)

Steps to reproduce

As the ga command prints the codepoint of the character under cursor, that should perhaps be reflected in its documentation at :help ga. Currently help says that it prints the ascii value of the character under the cursor.
Executing :lh code\_.point shows that in two places in the docs, specifically:

mbyte.txt|604 col 56-66| charsets, such as JIS X 0208, if this field is 0, code points has
print.txt|307 col 68-78| Also, some characters in the CJK ASCII code ranges differ in a few code points

the word codepoint is written separately. Perhaps that should be fixed for consistency as in other places its written in one word.

Expected behaviour

.

Version of Vim

9.1.1957

Environment

.

Logs and stack traces

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Dec 17, 2025, 5:25:00 PM (9 hours ago) Dec 17

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#18955)

As the ga command prints the codepoint of the character under cursor, that should perhaps be reflected in its documentation at :help ga. Currently help says that it prints the ascii value of the character under the cursor.

When I hear codepoint, I think U+... which is however not what ga prints. ga prints various informations about the character under the cursor in different encodings, but U+ is none of them, so I am a bit hesitant to call it a codepoint. Besides, it would raise the question what of the different outputs is the codepoint.

Regarding the other 2 spellings of codepoint vs code point, let me fix this right now

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Dec 17, 2025, 5:27:35 PM (9 hours ago) Dec 17

to vim/vim, Subscribed

Closed #18955 as completed.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Dec 17, 2025, 5:27:37 PM (9 hours ago) Dec 17

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#18955)

fixed as of 93d9d19

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

lkintact

unread,

Dec 17, 2025, 10:17:49 PM (4 hours ago) Dec 17

to vim/vim, Subscribed

lkintact left a comment (vim/vim#18955)

@chrisbra: Thank you, I've found another one (it's very minor so I'm not creating a new issue):

Line 8418 of options.txt says: M F Modified flag, text is ",+" or ",-"., however the described statusline item, %M, displays + and - without a preceding comma, so the line should probably be changed correspondingly.