Justin M. Keyes
Justin M. Keyes
# Problem - `dictwatcheradd` was originally added as a way to avoid the `options.c`, so we could use global variables instead of options. On the whole that was a reasonable...
# Problem Current situation: Nvim ships a few parsers (C, Lua, vimdoc, vimscript) in its runtime. If user wants more parsers they must build the parser and put it on...
### Problem For clients to get function signatures and type information, currently we need to model APIs in C. It's not easy for clients to generate their own language-specific interface...
https://github.com/neovim/lua-client will be mostly redundant after `nvim` itself has - `$NVIM` - `--connect` - `--remote`-like features - ergonomic Lua layer Then `nvim` itself could be used as the test-runner. Has...
# Problem https://github.com/neovim/neovim/pull/21472 removed `:hardcopy` in favor of `:TOhtml`, but `:TOhtml` requires extra steps. # Proposal Add a `:Hardcopy` command that does the following: 1. generates HTML 2. saves the...
In the past this was rejected because there is not a single GUI. But in practice, `has('gui_running')` is also used as a way to detect "is the TUI (not) running?"...
docs
todo - [x] fix `:trust` doc. [ref](https://github.com/neovim/neovim/commit/6752f1005d26c93a033d856a60b7b296f3e51634#r101699399) - [ ] nvim requires rpc responses in order. [ref](https://github.com/neovim/neovim/issues/19932) - [ ] [NVIM_APPNAME](https://github.com/neovim/neovim/issues/21691#issuecomment-1375542439) - cgroups blurb - UIs normally should NOT set...
# Continued in https://github.com/neovim/neovim/pull/12503 ? - [x] `nvim_log(level, message)` API function - [ ] update API clients (python, etc.) to use `nvim_log()` for critical messages - [ ] `stdpath('log')` ?...
see https://github.com/neovim/neovim/pull/4412#issuecomment-192544136 May help with https://github.com/neovim/neovim/issues/4349 # problem Lua/Vimscript plugins can't handle OSC codes emitted by `:terminal` programs. # solution - set up Lua callback dispatch via `vterm_state_set_unrecognised_fallbacks()` ? -...
## Problem: - No easy way to hook into: - vim.paste - vim.ui.x - LSP request/response handlers. (No mention of "before" or "after" in `:help lsp`...) - Hooking into functions...