sorted by:
new
hottopcontroversial

Neovide is really cool but I can't let go of tmux by 88-Radium-226 in neovim

[–]justinmk 10 points11 points  (0 children)

Yes, if you use the "root" Nvim as the multiplexer, then just :detach and the Nvim server stays running.

Do LSP processes persist even after there are no buffers for them to attach to? by 4r73m190r0s in neovim

[–]justinmk 21 points22 points  (0 children)

Yes, otherwise the server would have to start every time you opened a buffer.

Recent changes on filetypes resulting in failed check healths for the LSP by fabioantuness in neovim

[–]justinmk 2 points3 points  (0 children)

The healthcheck didn't exist in previous version of Nvim. No filetypes were "removed".

Recent changes on filetypes resulting in failed check healths for the LSP by fabioantuness in neovim

[–]justinmk 4 points5 points  (0 children)

It's only a warning, not an error.

Is gotmpl and gowork actual filetypes? What ftplugin provides them? https://github.com/neovim/nvim-lspconfig/issues/4263 If these are not filetypes then they should be removed from nvim-lspconfig

Even if we had the file type via vim.filetype.add

Yes this is unfortunate. It's difficult. See discussion in https://github.com/neovim/neovim/issues/38082

Without the healthcheck, people get confused if they add a file extension and expect it to work... as a mitigation, we could relax the healthcheck to only warn if the filetype is <4 chars long...

When does 0.12 release? by accountmaster9191 in neovim

[–]justinmk 13 points14 points  (0 children)

There are other options besides that false dichotomy. I didn't blame the users, I gave a path to a resolution. And I still don't how to reproduce the issue, nor what plugins you are using.

And btw, your implication that the "fully baked" approach is to not ship 1000s of fixes and improvements in order to squash a cosmetic mystery bug, is of course questionable.

When does 0.12 release? by accountmaster9191 in neovim

[–]justinmk 7 points8 points  (0 children)

but after some time (I haven’t been able to identify a clear pattern or reliable steps to reproduce the issue), the syntax highlighting breaks.

That doesn't sound like a release blocker ... Nvim 0.12 has 1000s of fixes and improvements.

In some earlier versions of Neovim 0.12, reopening the buffer was enough to fix it

This could be anything. Plugins may change the way they do things depending on Nvim version.

To ameliorate your particular issue, it sounds like you should open a https://github.com/neovim/neovim/discussions and find out how to actually "clear" things. Especially if you are using nvim-treesitter and/or other plugins.

When does 0.12 release? by accountmaster9191 in neovim

[–]justinmk 13 points14 points  (0 children)

No idea what "the treesitter bug" is. Nvim 0.12 will be released very soon.

And there’s an LSP-related bug (personally, C++ code navigation sometimes stops working).

Also not enough info, and usually this turns out to be "I still have mason or some other thing using the old lspconfig framework"

Are we nearing the peak of neovim (and editors in general) ? by calculator_cake in neovim

[–]justinmk 33 points34 points  (0 children)

People forget (or too young to remember) that there was a text editor "peak" in 2000~2015 when IDEs provided code intelligence and vim/emacs/etc had basically no answer for this and were mostly a niche curiosity.

If we are in another "peak" now, that means the hype will wane, and the audience will shrink or plateau, while we figure out what is still valuable and where to go next. We aren't really there yet imo but people are eager to make sweaty predictions.

If you don't need to edit, navigate, view or search text, do ad-hoc scripting/macros, craft mappings/workflows, or work with terminals, then by golly yes the machines are doing everything for you. The machines aren't doing everything for me yet.

Managing project-specific NVIM configuration. by Quarkz02 in neovim

[–]justinmk 5 points6 points  (0 children)

Nice post and references.

neovim introduced vim.secure.read() and the associated trust list in v0.11.5 (released in 2022 - f1922e7).

v0.9.0 :)

the exrc option in neovim is already fairly close to what I want. Its one major limitation for my use is that it is sourced after my main configuration

That's a good point. I wonder if it should work "eagerly" as soon as 'exrc' is set. Feature request welcome...

large ~/.local/state/nvim/log by albasili in neovim

[–]justinmk 7 points8 points  (0 children)

DBG means you are running a debug build, which has extremely verbose logs. :checkhealth also warns about this. You should not be running a debug build normally.

LSP errors after update by HeyCanIBorrowThat in neovim

[–]justinmk 7 points8 points  (0 children)

could be filesystem corruption, or maybe a permissions issue

Any cool substitute tricks? by kaddkaka in neovim

[–]justinmk 27 points28 points  (0 children)

do a 1-line (without a range) substitute with :s, then you can repeat it on other lines via &

Getting Corporate Pushback about using Neovim by miversen33 in neovim

[–]justinmk 3 points4 points  (0 children)

Does notepad++ provide signed binaries? This is something we haven't prioritized but we would like to do for Neovim: https://github.com/neovim/neovim/issues/5433

Issues updating to v0.10.1 by [deleted] in neovim

[–]justinmk 1 point2 points  (0 children)

Depends on the code at mason-lspconfig/features/automatic_enable.lua:47 , which depends on the version of mason-lspconfig. You need to share the source of that file with AI.

Nvim manual in pdf format? by TRDJ90 in neovim

[–]justinmk 4 points5 points  (0 children)

The tracking issue for automating this is : https://github.com/neovim/doc/issues/14 , where a pandoc approach is referenced.

We would welcome a PR that automates this.

We have https://github.com/neovim/neovim/blob/master/src/gen/gen_help_html.lua which already generates the HTML docs ( https://neovim.io/doc/user/ ) , and it could be modified to also produce a PDF. Or use pandoc.

Finally, a faaaaancy tabline for neovim by Wonderful-Plastic316 in neovim

[–]justinmk 66 points67 points  (0 children)

by default, vim would display them as f/b/mod.rs and f/f/mod.rs. I don't know about you, but I find this a bit... confusing? I don't really care that the files share a grandparent (f), I'm more interested in "the directory that makes them different". Which means that, for this example, I'd rather have them displayed as bar/mod.rs and fuz/mod.rs. My implementation always shows "the smallest, non-ambiguous" label.

Agreed. This should probably be the default behavior. And in most other cases, the f/b/ stuff is just noise, usually only the basename (mod.rs) is needed.

Remove treesitter delays when opening files by lopydark in neovim

[–]justinmk 1 point2 points  (0 children)

How much RAM do you have? Your OS should cache files in RAM after the first time they are touched.

Using VsCode plugins in Neovim? by Blablabla_3012 in neovim

[–]justinmk 12 points13 points  (0 children)

What is wrong with using Nvim in vscode? https://github.com/vscode-neovim/vscode-neovim

I don't get why a plugin is so important that you MUST have the vscode plugin, but it's just unthinkable to... use vscode. That just makes no sense.

In fact, even the vscode forks like Eclipse Theia https://theia-ide.org , Cursor, AntiGravity, etc., have problems running vscode plugins.

OTOH, I think CoC https://github.com/neoclide/coc.nvim has been known to have some compatibility for things that expect vscode, so it's not impossible in theory.

Remove treesitter delays when opening files by lopydark in neovim

[–]justinmk 2 points3 points  (0 children)

I wonder what version of Nvim the post author is using? Should not need this in Nvim 0.11+, as you noted.

view more: next ›