r/neovim

A while back I shared select-undo.nvim, a plugin to undo specific lines instead of the whole-buffer chronological undo. The early version had known bugs (reverting a line could impact its neighbor).

Finally after a year I got some time to make some changes. This update is a full rewrite of the core and it now works somewhat reliably (you guys can be the judge, because I might have tested in some bias scenarios).

What it does: edit line 10, then line 50. Native 'u' forces you to revert line 50 first. With this plugin you select line 10, press gu, and only that change reverts. Line 50 keeps your newer edit.

Mappings (visual mode):

- gu - revert the newest change in the selected lines; press again to step further back

- gU - revert the last change of every selected line in one press

- gC - revert only the selected characters, keeping other edits on the same line

What changed under the hood:

- Old version compared fixed line ranges across undo states, which broke when lines were inserted or deleted. Now it diffs each undo state and reverts only the hunks touching your selection

- A revert never touches lines outside your selection

- Each revert is one regular edit, so native u / Ctrl-r work on it as expected

- No more undo-tree pollution, works with undofile across sessions

- All mappings configurable

Repo: select-undo.nvim

Feedback and issues welcome. If you tried the old version and it bit you, this one is worth another look.

hi all!

a while ago i posted lytmode.nvim - a minimal, balanced colorscheme for neovim inspired by obsidian's LYT-Mode.

just like the original, there is no dark/light split: it's not dark, it's not light - it's the comfy middle.

recently i gave it a slight polish, so here is a small repost <3

github: https://github.com/github-main-user/lytmode.nvim
neovimcraft: https://neovimcraft.com/plugin/github-main-user/lytmode.nvim/

feedback, issues and ideas are totally welcome!

I've just been down a rabbit hole using Gemini to analyze why my nvim setup is consuming so many CPU resources when idle. This is a huge issue - I could potentially have many instances of nvim open, and each one using up CPU cycles carelessly adds up to a serious waste of CPU cycles and heating. My laptop has been too hot for months, and now I finally know why.

The main culprit? Plugin authors are setting repeating timers of 33ms, 50ms or worse without realizing the implication - they're constantly waking up the CPU and turning sleep into effective busy waits.

So far I've found:

• which-key sets a 50ms timer to bypass the lack of ModeChanged events on pre-0.10 Neovim. Completely unnecessary on 0.10+ and done without a version check.
• noice sets an indefinite 33ms timer on bootup.
• snacks' statuscolumn plugin runs a 50ms timer to refresh the status rather than responding to events.
• lualine sets a 50ms/16ms(!) timer by default.

All of these are included in Lazyvim, meaning that if you use Lazyvim, you've turned neovim into a CPU cycle-eating machine.

I don't want to keep hunting for high frequency timers in careless plugins. Something needs to be done, preferably at the nvim layer.

EDIT: Definitely didn't expect some people to be so defensive about this.

To clarify: timers aren't a problem in an application that already uses up your CPU a lot and needs to respond quickly. They are a problem in an application that sits in the background is supposed to let the CPU idle as much as possible. One can also run the timers when the app is active, and then disable them when it's idling. I have neovim running in tens of instances on my machines, and the impact is serious.

I'm attaching LLM answers as objective observers on the matter, since people want to dispute it:

https://chatgpt.com/share/6a4a2354-03e4-83ed-b745-2315e3b3e88f

https://share.gemini.google/vAll2XerOoso

https://claude.ai/share/95cec7cb-7078-4bd9-91c1-6f2f2009a325

EDIT2: I didn't mean this as an attack on anyone in particular (even if it was read as such), and I didn't do my homework enough to know 3 of the mentioned plugins are made by one guy, making it look like an attack. Seriously, this wasn't meant as a shaming or anything like that, no matter what intent you read into it. It's totally ok for any programmer to make this mistake - especially one as prolific as folke, and I appreciate his work greatly -- that's why I use it as my daily driver. My comment was meant at the problem where there is a lack of awareness in general about the problem of using high frequency timers, and there's no easy mechanism to trace them from the neovim side.

Hi everyone,

I just put together **matugen.nvim**, a plugin designed to bring dynamic Material You color palettes straight into Neovim via Matugen

If you're ricing your Linux setup with wallpaper-based color generation (like Hyprland, Waybar, etc.) and want your editor to match without clunky hacks or hardcoded scripts, this bridges that gap

Key Details:

• Integrates Matugen palettes directly into your Neovim environment.

• Lightweight and written entirely in Lua.

• Designed to fit seamlessly with broader system-wide dynamic ricing.

Check out the repo here: https://github.com/Senal-D-A-Gunaratna/matugen.nvim

Let me know if you have any feedback or features you want to see added!

After so much horrible times we all have living inside of iran, during internet blockage the only thing i can do was reading manuals on my system and updating my plugins so i gave a stable update to Neaterm. Give feedbacks if any problems or idea comes to you. Thanks

For the past 3 years, I’ve been a graduate student in computer science. Through connections I made at a conference I published at as a masters student almost three years ago (at the beginning of my degree), I learned about an open position in Amsterdam in which I would both conduct research and architect software. Im now a PhD student and this is the direction I want to go in.

My friends (researchers, no engineering experience) helped guide the content on the CV, suggesting to me the content that would be most useful. The bulk of it was, of course, publications, software I’ve worked on, and other useful background like designing and teaching university courses and reviewing papers for conferences (typically what researchers call “professional service”). But, I also wanted to include activities in open source to strengthen my software experience. My friends didn’t know for sure if it would help or just appear like fluff. I went with it and listed some activity with Neovim, like a plugin I wrote that has received bug reports and feature requests. That part felt important: having a plugin is okay, but participation from users feels strong.

I was selected for an interview and called out this experience, which they seemed to like. I nailed a second interview and landed the job. I emigrate from the U.S. on the Fourth of July. For all those here living in Amsterdam, let’s grab a drink sometime.

Most of the great DB plugins (vim-dadbod and nvim-dbee) are fantastic — until $DAYJOB hands you an Oracle or SQL Server box and the experience falls off a cliff. I was tired of alt-tabbing to SQL Developer / SSMS just to run a SELECT, so I built dblite.nvim.

You write SQL in any buffer, run it, and get paginated results in a split — named connections, typed bind params, history, exports, and schema-aware completion.

What it does

• Run the whole buffer, or just the statement under your cursor (treesitter-aware)
• Paginated result split with column types, query timing, and a per-session history you can page back through ([ / ])
• Named connections with $ENV_VAR password refs, stored chmod 600
• Typed bind params from a dblite.binds.json — numbers, auto-quoted strings, and raw SQL expressions
• Export the entire result set (not just the visible page) to CSV/JSON
• SQL autocomplete via blink.cmp — tables, columns, and bind names pulled from the live schema

The nerdy bit

Oracle/SQL Server drivers are JDBC — i.e. Java. I didn't want to make anyone install a JVM, so the DB layer is compiled to a native binary with GraalVM native-image and shipped pre-built. It's downloaded on install; there's no JVM at runtime. Falls back to a source build only if there's no binary for your platform.

Requirements: Neovim 0.11+ (optional: jq, telescope.nvim, blink.cmp).

Roadmap is MySQL next. It's early, so I'd genuinely love feedback — especially from anyone else stuck in Oracle/SQL Server land. Bug reports and "this workflow feels weird" takes equally welcome.

Repo: https://github.com/aaronshahriari/dblite.nvim

Most of my workflow already lives in Neovim — code, prose, notes, scratchpads. The piece that always lagged was querying the notes. Plenty of tools let me grep them; almost none let me ask things like "all the drafts under tasks/q2 that link to people/alice" without leaving the buffer.

Turns out you can. IWE is a Rust binary (LSP server + CLI) that treats a directory of .md files as a queryable graph. Install once, use it from the editor over LSP and from the shell over :!.

The query language is small and reads like Mongo's:

iwe find --filter 'status: draft, priority: {$gte: 8}'

iwe find --filter 'author.email: {$exists: true}'

Frontmatter is the schema. Markdown links are the relationships — and there are two kinds, which the engine actually distinguishes:

• An inline link in body text is a reference: "see also."
• A markdown link alone on its own line is an inclusion link: containment. The linked document becomes a structural child of this one.

Each gets its own pair of operators:

iwe find --references people/alice # docs that link to Alice inline
iwe find --included-by tasks/alpha:0 # everything under alpha's tree (unbounded)
iwe find --included-by tasks/alpha:0 --references people/dmytro --filter 'status: draft'

That last line: drafts under the tasks/alpha subtree that also mention people/dmytro inline. Three relationships, three flags.

The same predicates drive iwe count, iwe update, iwe delete. Bulk-set frontmatter from the shell:

iwe update --filter 'status: draft, reviewed: true' \
--set status=published \
--set published_at=2026-05-02

update and delete require an explicit --filter (no accidental whole-corpus rewrites). --dry-run previews.

From inside Neovim, this composes two ways.

The same iwe binary is also a markdown LSP server, so the editing side feels like working in code:

• gd — jump to linked notes
• gr — find references / backlinks
• K — hover preview of a linked note without opening it
• Code actions for extract section to a new file, inline a referenced note, rename
• Auto-complete for link targets as you type
• Inlay hints showing parent context and link counts

There's a dedicated plugin — iwe.nvim — that wires the LSP up and adds Telescope integration with hierarchical path search (notes show as Journal ⇒ 2026 ⇒ Week 18 ⇒ Mon notes). Lazy / packer / vim-plug all work.

For querying, you don't need a special integration — the CLI is enough:

• Output is plain text — pipe to jq, fzf, telescope, whatever.

Same install handles both: cargo install iwe and you have the LSP server + the CLI. The LSP runs against any folder of .md files; the CLI queries the same folder.

Side note: this also turns out to be a decent shape for AI agents. They use the same CLI you do, see the same files, and git log is your audit trail for whatever they touch.

Repo: https://github.com/iwe-org/iwe · Plugin: https://github.com/iwe-org/iwe.nvim

Curious what the heavy notes-in-Neovim crowd thinks, especially on the inclusion-vs-reference link split.

Repo: https://github.com/patrick-sharp/waypoint.nvim

I just released a neovim plugin I've been working for a while. It's a bookmarking plugin. I made it because I felt a lot of the existing bookmarking plugins were lacking some important features, including:

• The ability to reorder your bookmarks
• The ability to delete and move your bookmarks in bulk
• The ability to view lines of code around your bookmarks
• Syntax highlighting in the preview window
• Resilience to the content of files changing (e.g. checking out a git commit that changes the file contents won't delete your bookmarks)

If you have any feedback, please create a github issue or email patricksharp.dev@gmail.com

https://github.com/parwest/peeper-picker.nvim

v1.1.0 adds peek history to peeper-picker.

peek history

:PeeperPickerHistory opens a plain list of the symbols you recently peeked, newest first.

• <CR> peeks a name again, without moving your cursor or touching your current buffer. three files deep in a refactor, you can re-check anything you looked at earlier and not lose your place
• c clears the list (asks first), q/<Esc> close
• one entry per name, repeat peeks move it to the top
• session only, in memory, nothing written to disk. bounded by history_size (default 100, 0 disables)

renames

history pins each name to the spot you peeked it. peek oldName, rename it to newName, and:

• the list still shows oldName — you never peeked newName, so it doesn't pretend you did
• selecting oldName runs a text search for it, which returns exactly the occurrences the rename didn't touch: strings, comments, docs, files the server doesn't index
• a name that still resolves to a live symbol runs a normal full peek

also shipped in 1.0.0

• results grouped by file with folding: J/K jump between files, zo/zc/za/zM/zR work, <CR> on a file header collapses it
• ? opens a key cheatsheet inside the picker
• decl is its own tag now instead of sharing def

setup

{

  "parwest/peeper-picker.nvim",

  main = "peeper_picker",

  cmd = { "PeeperPicker", "PeeperPickerHistory" },

  opts = {},

  keys = {

    { "<leader>pp", "<cmd>PeeperPicker<cr>", desc = "Peeper Picker" },

    { "<leader>ph", "<cmd>PeeperPickerHistory<cr>", desc = "Peeper Picker History" },

  },

}

still zero external dependencies, but needs an attached LSP client.

would love any and all feedback,

thanks to everyone who has reached out with feature requests!

https://github.com/parwest/peeper-picker.nvim