neovim/runtime/lua/vim/_extui/cmdline.lua, branch masterVim-fork focused on extensibility and usabilityhttp://git.waynecole.info/neovim/atom?h=master2026-02-05T12:45:45Zrefactor: rename _extui => _core.ui2 #376922026-02-05T12:45:45Zluukvbaalluukvbaal@gmail.com2026-02-05T12:45:45Zurn:sha1:bf68ba40a03a19c97454ede293ed289c547b5aaa
Problem:
_extui module name is confusing and should eventually end up in _core/.
Solution:
Move it there and name it ui2.fix(ui2): don't adjust dialog pos for pum wildmenu (#37695)2026-02-04T12:15:34ZSean Dewar6256228+seandewar@users.noreply.github.com2026-02-04T12:15:34Zurn:sha1:9655bd560f6cce646e77e6ba1f75e7c08462fdf3
Problem: Dialog position unnecessarily adjusted for pum wildmenu.
Solution: Apply no offset if the pum is visible.fix(ui2): wildmenu hidden behind dialog window #376842026-02-03T13:17:33Zluukvbaalluukvbaal@gmail.com2026-02-03T13:17:33Zurn:sha1:3038f0191e9d7d681a1b6a936ed452b85815a247
Problem: The wildmenu is hidden behind the dialog window with "list" in 'wildmode'.
Global ('laststatus' set to 3) statusline is hidden behind the
pager window.
Solution: Check wildmenumode() to adjust the dialog position when necessary.
Ensure pager is positioned above the global statusline with 'laststus' set to 3.fix(ui2): start treesitter after deleting cmdline buffer (#36274)2025-10-22T14:16:36Zluukvbaalluukvbaal@gmail.com2025-10-22T14:16:36Zurn:sha1:c94b7b93c0d9f843be6b68db9dee0a0297060af4
Problem: Treesitter is not started in new cmdline buffer after deletion.
Solution: Start treesitter when highlighter buffer no longer matches.fix(extui): error on :call input('') (#35515)2025-08-27T15:12:17Zphanium91544758+phanen@users.noreply.github.com2025-08-27T15:12:17Zurn:sha1:cd7cf4bd16e79f3b8b28a8a86580d45b3cd151d4
Problem: Error on empty string prompt.
Solution: (prompt .. '\n'):gmatch('(.-)\n').feat(extui): support paging in the dialog window (#35310)2025-08-21T12:56:59Zluukvbaalluukvbaal@gmail.com2025-08-21T12:56:59Zurn:sha1:94677318655eb803fccef4409834b6b77e11282a
Problem: Unable to see e.g. `inputlist()` prompts that exceed the dialog
window height.
Multi-line prompts are not handled properly, and tracking
is insufficient for messages in cmdline_block mode.
Solution: Add vim.on_key handler while the dialog window is open that
forwards paging keys to the window.
Properly render multi-line prompts. Keep track of both the start
and end of the current cmdline prompt. Append messages after the
current prompt in cmdline_block mode.feat(extui): don't enter pager for routed message #346792025-06-27T19:13:01Zluukvbaalluukvbaal@gmail.com2025-06-27T19:13:01Zurn:sha1:f2988e05db451099645e32a427d5aaf4cae53bb4
Problem: Messages routed to the pager to be shown in full, enter the
pager automatically, yielding another "press-q-prompt".
Solution: Only enter the pager when requested explicitly. Otherwise,
close the pager on the next typed mapping, unless that mapping
entered the pager.perf(extui): delay creating windows, buffers and parser (#34665)2025-06-27T13:54:32Zluukvbaalluukvbaal@gmail.com2025-06-27T13:54:32Zurn:sha1:bfe42c84de053abe125f7a61116bc8a97ec32cde
Problem: vim._extui unconditionally creates windows, buffers and the
Vimscript cmdline highlighter when it is first loaded.
Solution: Schedule first creation of the window so that first redraw
happens sooner (still need to create at least the cmdline
window asap as it can have a different highlight through
hl-MsgArea; thus further delaying until the first event that
needs a particular target seems redundant). Load the cmdline
highlighter on the first cmdline_show event.feat(ui): emit "msg_clear" event after clearing the screen (#34035)2025-06-26T22:27:21Zluukvbaalluukvbaal@gmail.com2025-06-26T22:27:21Zurn:sha1:2b4c1127ad1c8cff38f562d71f411c35ec6ba8d6
Problem: ext_messages cannot tell when the screen was cleared, which is
needed to clear visible messages. An empty message is also
never emitted, but clears messages from the message grid.
Solution: Repurpose the "msg_clear" event to be emitted when the screen
was cleared. Emit an empty message with the `empty` kind to
hint to a UI to clear the cmdline area.fix(extui): clear cmdline buffer for first message (#34490)2025-06-15T10:55:01Zluukvbaalluukvbaal@gmail.com2025-06-15T10:55:01Zurn:sha1:5046ef4c8f8d738d90b220cf9a2e2a692bd266ba
Problem: Cmdline buffer is not cleared for a new message (since c973c7ae),
resulting in an incorrect spill indicator. When the cmdline
buffer is cleared, "msg_row" is not invalidated, resulting in
an error. The extui module is untested.
Return value of `vim.ui_attach()->callback` is undocumented.
Solution: Clear the cmdline buffer for the first message in an event
loop iteration. Ensure msg_row passed as end_row does not
exceed buffer length.
Add `messages_spec2.lua` to test the extui module, keeping in
mind that test coverage will greatly increase if this UI is made
the default. As such, only tests for specific extui functionality
unlikely to be covered by tests leveraging the current message grid.
Document the return value of `vim.ui_attach()->callback`, it seems
to make sense, and is also used to suppress remote UI events in
`messages_spec2.lua`.