neovim/runtime/lua/vim/termcap.lua, branch master

refactor: rename termcap.lua -> tty.lua #38437

2026-03-23T14:14:48Z

Problem: The `termcap.lua` module is too narrowly named. We may need a place for tty-related functionality in the future. https://github.com/neovim/neovim/pull/31399#discussion_r1882598297 Solution: This isn't a public/documented interface, so just rename it.

docs: use "ev" convention in event-handlers

2026-03-12T10:12:56Z

Problem: In autocmd examples, using "args" as the event-object name is vague and may be confused with a user-command. Solution: Use "ev" as the conventional event-object name.

feat(tui): add nvim_ui_send (#35406)

2025-08-22T20:05:43Z

This function allows the Nvim core to write arbitrary data to a TTY connected to a UI's stdout.

fix(tui): remove DCS escaping in tmux (#32723)

2025-03-06T03:28:05Z

Per https://github.com/tmux/tmux/issues/4386, tmux does not support DCS responses, even if the initial request was escaped.

feat(terminal)!: include cursor position in TermRequest event data (#31609)

2025-03-05T15:45:22Z

When a plugin registers a TermRequest handler there is currently no way for the handler to know where the terminal's cursor position was when the sequence was received. This is often useful information, e.g. for OSC 133 sequences which are used to annotate shell prompts. Modify the event data for the TermRequest autocommand to be a table instead of just a string. The "sequence" field of the table contains the sequence string and the "cursor" field contains the cursor position when the sequence was received. To maintain consistency between TermRequest and TermResponse (and to future proof the latter), TermResponse's event data is also updated to be a table with a "sequence" field. BREAKING CHANGE: event data for TermRequest and TermResponse is now a table

fix: another round of type annotation fixes

2024-10-31T11:55:23Z

feat(vim.validate): improve fast form and deprecate spec form

2024-10-21T10:32:06Z

Problem: `vim.validate()` takes two forms when it only needs one. Solution: - Teach the fast form all the features of the spec form. - Deprecate the spec form. - General optimizations for both forms. - Add a `message` argument which can be used alongside or in place of the `optional` argument.

docs: various fixes (#28208)

2024-04-29T23:04:42Z

Co-authored-by: Evgeni Chasnovski Co-authored-by: Famiu Haque Co-authored-by: Gregory Anders Co-authored-by: Guilherme Soares Co-authored-by: Jannik Buhr Co-authored-by: thomaswuhoileong <72001875+thomaswuhoileong@users.noreply.github.com> Co-authored-by: tom-anders <13141438+tom-anders@users.noreply.github.com> Co-authored-by: zeertzjq

refactor(lua): type annotations

2024-03-16T19:26:10Z

fix(termcap): set 'nested' on TermResponse autocommand

2023-12-14T17:38:34Z