neovim

mirror of https://github.com/neovim/neovim.git synced 2026-05-24 13:50:06 +00:00

Files

luukvbaal 5f7237f54b fix(ui2): unable to route by message ID #39734

Problem:  - "bufwrite" message identifier is encoded in the message ID
            of a "progress" kind message (since ff68fd6b); UI2 does not
            allow routing by message ID.
          - No documented way to set a default message target for all
            but a few kinds (without copying all of |ui-messages| kinds
            to cfg.msg.targets).
          - A user adding a message route for the documented empty ""
            kind can result in unexpected behavior.
          - Showing duplicate message (x) indicator in msg and cmd
            targets simultaneously is unsupported.
          - Manually triggering CursorMoved autocommand to add matchparen
            highlighting in the cmdline.
Solution: - Match cfg.msg.targets keys as Lua pattern to a message ID.
          - Recognize "default" as key in cfg.msg.targets, drop the
            undocumented cfg.msg.target field.
          - Don't try to get configured target for "" message kind/trigger.
          - Maintain msg indicator virtual text for the cmd and msg target.
          - Add matchparen highlighting by directly calling the Lua module
            (possible since b813c7e0).

2026-05-11 18:17:04 -04:00

ui2

fix(ui2): unable to route by message ID #39734

2026-05-11 18:17:04 -04:00

defaults.lua

refactor(defaults): use public treesitter select()

2026-05-09 10:00:03 +02:00

editor.lua

fix(lua): vim.wait(0) does not call loop_poll #39679

2026-05-10 14:22:31 -04:00

ex_cmd.lua

refactor(excmd): pass fargs to Lua for builtin cmds #39528