[vim/vim] runtime(doc): fix pattern problem in cmdline.txt (PR #19322)

3 views
Skip to first unread message

Mao-Yining

unread,
Feb 3, 2026, 9:47:49 AM (18 hours ago) Feb 3
to vim/vim, Subscribed

Problem: These examples are wrong.
Solution: use right examples.

Seems CmdwinEnter's pattern doesn't follow file-pattern.

@girish Since you changed this line before, could you please check whether
this work on your machine?


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/19322

Commit Summary

  • 63481a6 runtime(doc): fix pattern problem in cmdline.txt

File Changes

(1 file)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19322@github.com>

Christian Brabandt

unread,
Feb 3, 2026, 10:29:39 AM (17 hours ago) Feb 3
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#19322)

I believe the second example should have been accurate. Did this not work for you?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19322/c3842001886@github.com>

Mao-Yining

unread,
Feb 3, 2026, 10:40:24 AM (17 hours ago) Feb 3
to vim/vim, Subscribed
mao-yining left a comment (vim/vim#19322)

I believe the second example should have been accurate. Did this not work for you?

No. I have re-test it on gvim --clean 9.1.2125 MS-Windows 11. It is not work for me.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19322/c3842052864@github.com>

girish

unread,
Feb 3, 2026, 11:54:08 AM (15 hours ago) Feb 3
to vim/vim, Subscribed
girishji left a comment (vim/vim#19322)

All of these work for me, but I don't use windows. Maybe @habamax can take a look.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19322/c3842427617@github.com>

Reply all
Reply to author
Forward
0 new messages