Help with Setting up esp32 nvim plugin
(Need Help)

I am trying to setup nvim's lsp server to be able to properly work with esp idf toolchain project with my esp32. Anyway i came across this awesome plugin for this use case specifically. I got most of the things setup properly and now LSP suggestions are working with esp specific headers and libraries. But i am facing different issue with standard C header. For example-

https://preview.redd.it/l1n418eumexh1.png?width=715format=pngauto=webps=de6eccdef4cea8280f8966ce8cb3ad63ef30b4fa

digging through some gemini responses and other internet stuff i found out about clangd args and added those. Here's my final config's section for esp32.nvim for context-

https://preview.redd.it/kt8k5whemexh1.png?width=623format=pngauto=webps=20ee7e7fb713c6935cfffeb23083c835ad0dedac

So if someone can help me to figure out how get the whole setup working with both esp specific libraries and normal standard C libraries too.


By the way on a side note a the documentation on the esp32 nvim github was very detailed and clear. Thanks to the developer of that project if this post ever reached you.

https://redd.it/1xe6rq5

@r_neovim

Current state of Java LSP implementations
/r/java/comments/1xeizqt/current_state_of_java_lsp_implementations/
(Random)

https://redd.it/1xezauz

@r_neovim

LazyVim python 3.15 support, LSP config issue
(Need Help)

I did a clean install of LazyVim and added the python language extra. I did this to help debugging some configuration issues I had with my current longstanding LazyVim configuration.

I added no plugins nor did I do any configuration outside of LazyVim for lsp.


However, when I load a python file into nvim, it runs ty as an lsp server. In addition, the ty that it runs is really old--version 0.0.9 instead of the 0.0.35 I have installed in my path.

The result is a lot of diagnostic errors in the file.

What caused ty to be run when I didn't ask for it, and I think that the only python lsp server that LazyVim Extras loads is pyright? And where is it getting the old version of ty.

I don't understand!

https://redd.it/1xen28c

@r_neovim

gruber-darker-renaissance minimalist colorscheme
(Color Scheme)

I've used gruber-darker as my daily theme for a long time.

I love the original, but in long sessions the bright yellow and red kept pulling my eye, and the comments were as loud as the code. So I kept the same idea and color roles and toned everything down. The background is pure black now, the accents are softer and equally bright, and comments are a quiet gray.

https://github.com/kryptamine/gruber-darker-renaissance

Thanks to blazkowolf for gruber-darker.nvim and to Jason Blevins for the original Emacs theme.

https://redd.it/1xfe050

@r_neovim

Yet Another Vim Blog
(Blog Post)

Posting here because I use neovim as my daily driver but the majority of content is vim native.

Some content is written as a follow along, others just ranty. Im going to be releasing a post every week (until it inevitably ends up in the internets blog graveyard)

https://blog.nerdware.ca

https://redd.it/1xf6mb0

@r_neovim

rust-analyzer semantic tokens were eating ~80ms per keystroke on one 11k-line file and I didn't notice for months
(Need Help)

I kept blaming my plugin list for typing jank in one particular crate, but it only happened in our big codegen'd module. Turned out every text change triggered a full semantic tokens refresh, and with \:lua vim.lsp.set\_log\_level("debug")\ plus timestamps in the log I could see the request/response gap sitting at 60-90ms, right in the path of the next redraw. Killing \client.server\_capabilities.semanticTokensProvider\ in an \LspAttach\ autocmd for buffers over \~5k lines made it instant, and I lose almost nothing visually since treesitter already handles most of the coloring I care about. What I'd actually like is a size- or latency-based toggle rather than my hardcoded line count — has anyone wired up something that measures actual response time and degrades features automatically? Also curious if the same thing bites people with inlay hints, since those fire on the same edit path and I disabled them years ago out of taste rather than measurement.

https://redd.it/1xfaohy

@r_neovim

TIL `vim.lsp.buf.format` was silently doing nothing on big files because of the default 1000ms timeout
(Need Help)

Spent an hour thinking my conform/null-ls setup was broken on one repo — formatting worked everywhere except a couple of 3k-line TSX files. No error, no message, buffer just unchanged. Turns out the synchronous format path gives up after \timeout\_ms = 1000\ and returns false without telling you anything; prettier on those files takes \~1.4s cold. Bumping it to 3000 fixed it, but I ended up switching that filetype to async format-on-save with a \BufWritePre\ guard instead, since blocking the editor for a second and a half on every save was the real problem. Is there a reason the default is that low, or am I just the last person to hit this?

https://redd.it/1xfax21

@r_neovim

extmarks vs real lines ( performance )

https://redd.it/1xfn11f

@r_neovim

Kulala.nvim - GraphQL Explorer, Performance gains, Tree-sitter tweaks, Search requests
(Plugin)

Hello fellow Neovimmers 👋🏽,

Kulala has jumped to v7 and comes with some nice additions.

We tweaked the Tree-sitter grammar so that GraphQL and JSON bodies with unquoted variables are correctly highlighted and don't break the tree anymore.

Performance gains are getting released this week, which brings us near raw curl calls in regard to measured time that a request takes to run.

On average, it took more than 120ms to proxy the request through core and come back with the result and display it in Neovim. With the upcoming release, we're now averaging 80ms with an average of 72 when you run the same request via curl without any proxy involved. That's a big win.

There are always two sides, so the downside is that the backend supports a daemon mode now, which in turn reserves around 90-100 MB of your memory. The backend is not just for running the requests, but also for LSP like functionality.

For the peeps working with GraphQL you're pretty much used to having a tree like file explorer view. We already support this in a basic version for OpenAPI specs (think of it as Swagger Web UI but in Neovim), and with the next release, you get the Explorer View you all love from Postman in Neovim as well.

Last but not least, all Kulala tools feature a global, system wide request search now.

For those, who don't know what Kulala is:

A fully-featured HTTP/GraphQL/gRPC/Websocket-client interface for Neovim, that supports the Jetbrains .http spec (with full scripting support).

Kulala is swahili for "rest" or "relax."

It allows you to make HTTP requests from within Neovim.

In short: Bruno/Postman, but in your favorite Editor (and as a standalone desktop app, a vscode extension, a CLI, a formatter, linter and converter) and built upon the well defined .http format, instead of re-inventing the wheel and build yet another format.

https://github.com/dont-be-evil-company/kulala.nvim

https://redd.it/1xg890h

@r_neovim

Rethinking ai assisted programming driven by neovim and herdr
(Plugin)

I am trying to rethink actual "ai assisted" programming, where modern models, which are smart enough. So I try to emulate the flow where "llm can join" your current session and "behave" as if it's a remote pairing programming, rather than machine that generates enormous amount of code. Because what is called "ai assisted" right now it's hard to work with, because of enormous amount of code, that clanker spits on your face, so I want to bring human agency back, at least for myself.

https://makefunstuff.github.io/pairing-buddy/ \- you can check actual idea and try plugin here.

https://redd.it/1xg4mli

@r_neovim

custom colorscheme built off carbonfox
(Color Scheme)

I wanted to write a custom colorscheme because i was dissatisfied by every single one i could find and i also didn't want an extra plugin just for a stupid colorscheme

carbonfox was the closest to the colorscheme i wanted, so I took the specific file from the Nightfox repo and asked AI to turn the freaky color stuff they did into a hex code. Then I manually edited the hex codes to look similar to carbonfox, and modified what I didn't like. The result is what I call "oxidefox" because I'm funny

For those who want to include this in your config, literally just add this file and you're set

Good luck have fun :D

https://redd.it/1xg2o0j

@r_neovim

No command-line completion after :cdo
(Need Help┃Solved)

When you do :cdo, no completions are generated for command that follows.

Example: :cdo %s/foo/bar/g, after :cdo %s<Tab>, I don't get suggestions for commands with the letter s.

Is this a bug?


:help cmdline-completion

https://redd.it/1xg952q

@r_neovim

Weekly 101 Questions Thread
(101 Questions)

A thread to ask anything related to Neovim. No matter how small it may be.

Let's help each other and be kind.

https://redd.it/1xgknrl

@r_neovim