Hi r/neovim !

I'm learning a Rust library named Dioxus. When I was following along its tutorial, there's some code disabled in the default Cargo feature.

In Neovim, said code has no hints or diagnostics from Rust Analyzer. There is no useful information to tell me what is going wrong. However, when I open the same file in VS Code, the reason is clearly stated in a pop.

After digging into Rust Analyzer's doc a little bit, I found that I could set a flag to make Rust Analyzer recognize all features.

So My question is not about this particular problem about Rust Analyzer, but rather, how do I get the same information (telling me that "code is inactive due to ...") in Neovim?

Thank you for your help!

I kept ending up with 3-4 terminal splits open just to run backend + frontend + worker for the same project, and losing track of which one was still running or had crashed. So I built procman.nvim to manage that from inside Neovim instead.

What it does:

- Auto-discovers services in your workspace: package.json, Cargo.toml, go.mod, and .NET (.sln/.slnx/.csproj) — no config needed for the common case.

- Side panel showing status (running/stopped/failed/starting) and memory usage (RSS, including child processes) for every service, grouped by ecosystem (.NET / Node / Rust / Go / Custom) in collapsible sections.

- Start/stop/restart individual services or all of them at once, straight from the panel.

- Per-service logs (stdout/stderr) in a floating window.

- :ProcManAdd — add a custom command via prompt without hand-editing config.

- Per-project config via .procman.lua (auto-generated template with what was discovered) if you need to override anything, merged with your global setup().

https://github.com/Anderson-Vilela-op/procman.nvim

-- lazy.nvim

return {

"Anderson-Vilela-op/procman.nvim",

opts = {},

}

It's fresh (first public release), so bug reports, feature requests, and PRs are very welcome. Curious what workflows people have for this today — toggleterm + manual splits? overseer.nvim? Something else entirely?

Hey all,

I recently re-wrote the popular LazyGit plugin that is often recommended here for integrating LazyGit into NeoVim. I was using it for some time but since I only started using NeoVim, I was not very experienced in configuring it but overtime I noticed many issues the plugin has

I raised an MR with a fix for one of the issues but while fixing it, I realized the codebase is very bloated and was suffering from the burden of legacy support, so, I have forked and overhauled the codebase and added a few meaningful QoL improvements, namely:

1. Instead of using vim.g.* for configuration, it now uses the conventional setup({}) function
2. Plenary-based windows no longer spawn new lazygit processes, while leaking older ones (this was the issue my MR focused on).
3. You can now use * wildcards to specify custom lazygit configurations (in case you divide them into multiple files or whatever).
4. Plenary based buffers, as with regular buffers, now get custom buffer and window properties. This was not done in the older code for some reason.
5. Replaced legacy VimScript FFI calls (such as through vim.fn.* methods) with vim.api.* wherever possible.

The only major trade offs are:

1. No more Vim support (I removed all VimScript code)
2. Needs NeoVim 0.10 >=

Link to my fork: https://github.com/103sbavert/lazygit.nvim

Also, AI was used, but for adding LuaCATS doc comments for type hints and completions, to re-arrange already finished code into different files (without changing its internals or logic), and to understand the previous code structure but every line of code is hand crafted and well understood by me. If you find any issues, please report them. This was a major re-write so some things may have fucked up, let me know if that's the case.

Also, I hate vibe coding, so rest assured, this is not one of those shitty AI-slop plugins.

Hi everyone!
I'm excited to share with you new plugin: hover-notes.nvim

The main goal of this plugin is to add the ability to attach notes to words and view them in a floating window

The same note is displayed for every occurrence of this word (in the same category), not only in specific line/file/buffer

Features:

• Notes can be grouped by categories with the same formatting
• A category can be set for a workspace, a buffer, or an individual file
• Retrieves the closest matching word (up to a difference of half the word's length)

**UDPATE: There is now also a token-ultra variant of the theme**

Hello everyone

I have added 2 new variants to Token that are a bit cooler compared to the classic version of Token. These variants are also generated for all themes in /contrib in the GitHub repo.

Installation and configuration instructions are on GitHub https://github.com/ThorstenRhau/token

I hope you enjoy the theme

Hey, everyone!

I've finally finished putting a collection of colorschemes I've been working on. They're inspired by traditional colors from Formosa and Nippon colors, with 8 variants across both dark and light themes.

Welcome to review, test, report bugs, or submit pull requests!

Repos:

- Neovim: https://github.com/WeiTing1991/suannhai.nvim

- Part of main color schemes: https://github.com/WeiTing1991/suannhai-theme

Hey, everyone!

I've made a fork of https://github.com/oskarnurm/koda.nvim/ with RWTH-uni colors (because they are blue and nice). Thought that maybe someone else would like to take it for a spin! There are also couple of extras like themes for ghostty and kitty + some of my settings for `mini.pick`, `mini.files` and `telescope` to make them pop up.

Please tell me your thoughts (I'm pretty sure it is not for everyone) and if you find something broken and can fix it, please do! Literally everything is broken, I'm sorry...

Repos:
- https://github.com/mryodo/rwth.nvim
- https://codeberg.org/mryodo/rwth.nvim

PS shout out to incredible u/echasnovski and u/karnurm for their work!

Excited to share my first neovim theme, Scotopia (SayanShankhari/scotopia).

It's main goal is to be dead simple yet low eye strain for long coding sessions.

The colors are inspired by following well known themes,
"folke/tokyonight.nvim"
"ellisonleao/gruvbox.nvim"
"craftzdog/solarized-osaka.nvim"
"rebelot/kanagawa.nvim"
"Aejkatappaja/cendre"
"catppuccin/nvim"
"nyoom-engineering/oxocarbon.nvim"
"elvessousa/sobrio"

Upon trying out many color combinations for now settled in with only two theme variants: mahogany (dark) and hazelnut (light). Might be ugly for somebody but changes are heartly welcomed along with the reason details.

Later on will add more themes and fix existing theme issues.
Also i have two tiny custom libraries incoming into this project, "SayanShankhari/colorlib" and "SayanShankhari/colordot.nvim".

Any kind of help or contributions growing this project will be much appreciated.

Hi! Me again :]
I'd love to share my progress on tree-sitter-rocq

https://github.com/aruzdh/tree-sitter-rocq

Pre-release 0.2.0 focuses on mirroring some rules from the official reference manual, so anybody who wants to contribute or give it a look can have a better understanding by following the official grammar.

Plus, I'm currently working on (SF) Imp and (SF) Hoare Logic! This will be a great improvement, especially for those who use SF to learn Rocq.

Here is a preview of those features. Any suggestions, comments, or stars on GitHub would mean a lot!