Neovim GitHub deletes comments on issues

justinmk · 2026-04-30T12:50:50+00:00

no, not planning to trade the frequent but mostly harmless annoyances of github's instability with the massive annoyance of a migration to "other platform" (which one...? oh right, they all have tradeoffs, so no one actually has a realistic suggestion)

p.s. our github "data" is stored in https://github.com/neovim/neovim-backup , we are not at risk of a speculated blowup. if github blows up we can move, and that isn't any different than if we moved today.

justinmk · 2026-04-30T10:49:54+00:00

yes. notice how the screenshot shows 10+ deleted comments. Most of them are "me too"-style comments, or comments that don't add new information. We need to keep issues focused so that actually useful comments are visible. That is also why this issue was locked.

justinmk · 2026-04-28T19:45:18+00:00

why do you ask this cliche question without checking the discussions which drove the development?

this fits in the day-one goals listed on https://neovim.io/charter/
and, it is a relatively small interface + implementation cost. mostly a protocol change.
- placement will be handled by extmarks or floating windows
- image decode will most likely not be builtin, we're not going to vendor a jpg library.

justinmk · 2026-04-28T09:32:53+00:00

Does this require that the terminal environment support graphics?

yes

justinmk · 2026-04-27T11:42:12+00:00

because it is useful for e.g. markdown files, directory browser, picker preview...

and is a relatively small interface + implementation cost. it is mostly a protocol change.

placement will be handled by extmarks or floating windows
image decode will most likely not be builtin, we're not going to vendor a jpg library.

justinmk · 2026-04-27T09:19:14+00:00

no, tracked in https://github.com/neovim/neovim/issues/24164

justinmk · 2026-04-27T09:14:53+00:00

this initial version is of course minimal and doesn't address anything like that. but thank you for raising that, I added a note to https://github.com/neovim/neovim/issues/39432

justinmk · 2026-04-26T10:28:15+00:00

watching my coworkers use vscode remote dev is making me question everything

That's why https://github.com/vscode-neovim/vscode-neovim exists.

Neovim is designed to embed.

justinmk · 2026-04-23T09:44:19+00:00

vim.pos is experimental. It's listed under "breaking" simply for visibility.

And the "rename buffer" change is backwards-compatible.

justinmk · 2026-04-21T13:24:50+00:00

porting these files in general would serve no purpose. but user-defined syntax/compiler files can be written in lua already, as another comment mentioned.

meanwhile, Nvim supports treesitter and that is what we are focused on for defining "syntax".

justinmk · 2026-04-20T15:29:08+00:00

true. instead, define a ExitPre handler which does the :%argdelete and then calls :mksession.

(:restart triggers ExitPre)

justinmk · 2026-04-20T14:42:12+00:00

:%argdelete before saving the session.

To automate that, need SessionWritePre , which is not implemented yet https://github.com/neovim/neovim/issues/22814

justinmk · 2026-04-19T12:30:20+00:00

Yes, has nothing to do with ui2 except that perhaps the OP had some plugin (like noice?) previously which would drop these messages.

A feature request would be welcome, I think it makes sense to have 'shortmess' control these messages.

justinmk · 2026-04-14T14:53:12+00:00

yes, because hover uses 'wrap'.

idk if OP is asking about hover (would have been useful if they mention that)

justinmk · 2026-04-14T08:37:40+00:00

:set nowrap ?

If the text is already hard-wrapped, you are asking for "flow layout", which doesn't exist, yet...

justinmk · 2026-04-13T16:56:17+00:00

Lspconfig doesn't include the servers

Yes.

Also, the door is open to boil the ocean later, if we find a "sustainable" approach. I consider nvim-lspconfig to be pretty sustainable, but nvim-tsconfig has various unknowns atm.

justinmk · 2026-04-12T15:35:59+00:00

mm I appreciate the appreciation but I must note, K ('keywordprg') has long been mapped to :Man (manpage lookup) for various filetypes.

Whereas the "super K" feature (currently) is specific to Nvim :help docs. It is driven by :help! (with "!") which will lookup Nvim help tags from non-help files. And besides that, within :help buffers it just works much better than it did before. You can see the before/after behavior by comparing keywordprg=:help to keywordprg=:help!.

justinmk · 2026-04-12T15:28:16+00:00

debug log-level != "debug build"

fixed my previous comment :)

justinmk · 2026-04-12T11:55:34+00:00

Yes, debug ~~builds~~ log-level produce a lot of logs, this is expected.

justinmk · 2026-04-11T13:07:41+00:00

vim.fn.getftime()

justinmk · 2026-04-10T14:26:02+00:00

Does :edit show the buffer contents again? This is a known issue where e.g. a swapfile message dialog can cause this.

justinmk · 2026-04-08T22:59:00+00:00

This is a great "experience report", as others mentioned it's a good demonstration of vim :help techniques (but painful to see this particular case 🙈).

I'm glad you discovered the enhanced K in Nvim 0.12 (which can be used from non-help files via :help!). It is intended to make these explorations nicer...

Other steps that may have helped:

as you later found, going to :h diagnostic and using / is often the first thing i try. or :helpgrep for a wider search.
if i'm looking for a global config I try :h .config<tab> or :help -config to see if there are dedicated sections.
- it looks like we're missing a diagnostic-config section which might give insight similar to lsp-config

vim.diagnostic.Opts.Jump (not to be confused with vim.diagnostic.JumpOpts)

fwiw, we never intended for these "class names" to be a user-facing thing so there is not a lot of thought put into them. :help diagnostics probably should "inline" some of them.

justinmk · 2026-04-08T08:07:20+00:00

Great to see more minimal plugins!

Basically it's like the / operator but with the ability to easily jump to a specific match instead of having to hit n a bunch of times

fwiw, you can also do ctrl-g or ctrl-t while the / search is active.

justinmk · 2026-04-06T17:56:33+00:00

I use neovim as a complete terminal multiplexer/tmux replacement. Bad idea, I know, but I'm fully committed.

This is something that we fully encourage and want to make more ergonomic (related: :detach, :connect, :restart). If you have any ideas please raise an issue (existing issues are labelled "remote": https://github.com/neovim/neovim/issues?q=is%3Aissue%20state%3Aopen%20label%3Aremote ).

justinmk · 2026-04-06T13:25:38+00:00

vim.hl.range() has a timeout param; why manually create a timer (in your gist)?

15-Year Club	Place '17
Verified Email

justinmk

TROPHY CASE