This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/RussKazik on 2025-06-20 15:42:21+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/rainmanner on 2025-06-20 05:19:38+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/dahhakd on 2025-06-19 03:55:56+00:00.

I've recently migrated from vs code to neovim and so far I'm loving it, safe to say I'm not going back.

One feature that I miss though is devcontainers support. I used to not have anything at all locally installed and do everything inside containers, which vs code makes it very easy to do.

I'm trying to achieve something similar to devcontainers with neovim, so I've spent the last couple of weeks working on a little tool to automate the setup of neovim inside a running container. Basically this tool downloads and compiles neovim inside the container, along with a few other tools such as curl, fd, rg, etc and also your configuration. It uses static builds of all tools and compiles neovim with the new zig build, so it's completely independent of the container distro, in fact it doesn't install a single os package, and it works even on old distros like Ubuntu 16.04.

Note that I've tested only on Linux. It has builds for Mac, but they are unlikely to work due to a few missing features.

Here's a little demo: https://asciinema.org/a/juXKraph4GARMnTtfsGhVyd44

The tool: https://github.com/davidrios/nvim-mindevc?tab=readme-ov-file

See the answer to MufasaChan for a bit more context.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/neoneo451 on 2025-06-19 03:23:23+00:00.

This came to me last night in the shower. Gonna be a bit of a rambling

TL;DR:

• writing or maintaining a plugin is the best way to learn neovim.
• should we have a community project like lunarmodules and preservim to handle abandoned projects?
• obsidian.nvim wants more maintainers.

I took over obsidian.nvim community version for about three months now. I have been devoting a lot of time to it. And have been really enjoying working out things like making better CI/CD, building a simple cache system, and just fixing bugs. I am just a hobbist programmer, if not taking over an existing project with a large userbase, I would not get to have the experience with building with a community and delivering code that actually gets used by a lot of folks.

However, I just can not stop thinking about the original author. As you may know, the fork did not occur until months of no response to any issues/PRs and requests for adding new maintainers. So the new fork had to be slowly discovered by folks and then migrate. (we are going to detach the fork at some point)

At the same time, the original author is very active on github. In my mind, I just assume it is absolute burntout to make him not look at the repo ever again, or he just found a passion for other things that is so great that his is not seeing other things for one sec. Anyhow, we do respect that.

That leads to the issue about sustainability. I think it would be good to have tj's two most famous projects that are handed to the community is a good case study for my points.

• telescope.nvim: it has a lot of issues, but most of them has discussions, and there's active maintainers like Conni2461 that are devoted enough to have more contribution than tj.
• plenary.nvim: I think it suffers from the huge scope and the fact that it is more for plugin developers and not the users. So once the original author is not there, most of the issues gets unanwserd, and things like documentation has been not great.

So lessons for sustainability:

1. less scope per plugin. I intend to later delete obsidian.nvim's markdown rendering capability, since there's great plugins out there, and code about extmarks are just hard to read.
2. add more contributors when the plugin is on the upperward trajectory, so that they grow with the project and get positive feedback.

Moreover, I think it has come to a point where we have an organization like lunarmodules and pervervim, where folks can transfer their abandoned projects to, or people who want some experience making plugins can takeover from there.

there's two types of posts I see often, I think signifies a supply and demand mismatch:

1. asking if xxx.nvim is dead, because it is unmaintained.
2. poeple just wanting to make a plugin, asking for ideas, or they simply make a small plugin and move on, nothing wrong about that, just saying some of those folks can maybe spend some energy maintaining an existing plugin they love.

What do you think?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/HereToWatchOnly on 2025-06-18 08:37:18+00:00.

Ok hear me out, I've been using tokyonight for a while now since it has extensive support for other plugins and goes well with all the plugins folke creates. But I feel like it's too contrast-y, too much popping colors, same with catppuccin.

I wanted something muted so I tried nord, nordic, gruvbox, monokai, everforest, nightfox and rosepine but all of these don't have a good defaults (kinda) IDK what it's called but tokyonight and catppuccin gives the best OOBE.

While I could dig into the theme I like but I just want a good OOBE what's your pick?

I just want something with muted colors, good color distinction and greate OOBE

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/Somebody0184 on 2025-06-18 21:29:39+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/adelBRO on 2025-06-18 09:37:06+00:00.

Title might sound a bit crazy but I recently replaced Telescope with fzf-lua and it felt bad because I just like TJ as a dude. It's the reason I held onto Telescope for long after fzf-lua's release. Anyone else feel like this?

Side note - fzf-lua is so amazing, how does it even work that quickly.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/4r73m190r0s on 2025-06-18 09:21:58+00:00.

I'm using lazy.nvim as my package manager, and for some plugins I just have simple config with return { "user/repo" }, while some require calling setup function. Why is this the case, what happens in the background?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/chickichanga on 2025-06-17 14:31:07+00:00.

Demo

I was frustrated with my todos all the time. Wanted something that just works without any BS along with it. So, I created this dead simple plugin that just works, stores your todo on a markdown wherever you want and feel free to fork it and use it however you want.

I hope you will find this useful.

What it does:

• Floating window interface - Opens todos in a clean floating window that doesn't disrupt your workflow or you can open it in a separate buffer
• Auto-sorting - Automatically keeps incomplete tasks at the top, completed at bottom
• Bulk operations - Mark all done/undone, clear completed items with one keystroke
• Markdown format - Uses standard - [ ] and - [x] checkboxes
• Smart persistence - Auto-saves when you close the floating window

Key features:

• Dual display modes (floating window or buffer)
• Customizable keybindings and file location
• Full command support for users who prefer :TodoOpen over keybinds
• Works with any markdown file

I just wanted something that doesn't require any setup and let's me manage my todo without leaving the editor without a need of one more app or login to anything.

Link to plugin on GitHub: https://github.com/zaffron/todo-md.nvim

Perfect for developers who want a distraction-free way to manage tasks while coding. What do you think? I know some people might say, "Just use obsidian or why not just open a buffer and write todo" but for me todo is simply something I want to take a look at for reference not for storing as an archive to later come and look in distant future.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/marjrohn on 2025-06-18 03:04:19+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/_rand0m_guy on 2025-06-16 20:52:42+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/mplusp on 2025-06-17 22:42:32+00:00.

Not sure if I should post every new video in this series here or if it's becoming too spammy. Let me know!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/mplusp on 2025-06-16 07:21:18+00:00.

So the format is a little different again, as I put together some short insert mode related tips. I also tried to minimize the cuts a little and tried another screnn recording tool. Hopefully these changes result in better audio sync. What do you think?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/Worried-Difficulty-4 on 2025-06-16 16:18:34+00:00.

Hi Team,

I have been using NeoVim for a few years now and ditched my heavy electron-based IDE long ago. The other day I decided to make a lite-weight config for servers/when my full NeoVim config is overkill.

I made a video which might be useful for newcomers here: https://youtu.be/skW3clVG5Fo

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/BIBjaw on 2025-06-16 16:05:08+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/siduck13 on 2025-06-16 23:39:21+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/Spelis123 on 2025-06-16 18:41:11+00:00.

If you ever wished you could just open a .db file in Neovim and actually get something readable instead of binary garbage, now you can! (well, there are other plugins too but...)

i built nvim-dbview - a dead simple and lightweight Neovim plugin that lets you edit and browse databases from several database backends

It's great for Flask/Django devs, game devs, or literally anyone who's sick of switching to external DB viewers just to peek at a row. Also good if you feel like other alternatives are too complex or whatever

Give it a try and let me know if you like it, find any bugs or want any more features.

Cheers!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/mahmirr on 2025-06-16 03:03:22+00:00.

Link: https://github.com/nix-community/kickstart-nix.nvim

If you haven't checked it out, you should! It's how I'm going to be using to teach newbies at school for setting up their Neovim environments.

One of the big mistakes I made was not learning about :Tutor soon enough, and using a pre-built flavor of Neovim like LunarNvim, LazyVim, and AstroNvim. The latter was the best. But, I would constantly face issues, and forbid me from ever updating my packages or anything on my system.

Now, though, with kickstart-nix.nvim, since it uses Nix to set up the environment on your PC, you have extremely strong guarantees for the plugins and dependencies that you are using in your project, and you can instantly move your configuration between computers, no bullshit dealing with external dependencies.

Sharing this so that more people hop on the train.

I've used nixvim, NixCats, and a bunch others. The simplest (and arguably best) has been kickstart-nix.nvim.

In terms of plugin availability, you can check them on Nixpkgs: https://search.nixos.org/packages

Packages are being added and updated quite frequently, and you can easily target specific commits or specific forks of your favorite Vim/Nvim plugins.

Feel free to ask questions, and I'll try my best to answer.

To be clear, I'm not shitting on anyone's parade. Just want people to be aware of an alternative that I think is simpler and easier for newbies to get started with and on their path to customizing their environments exactly how they want.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/Difficult_Square5051 on 2025-06-16 13:39:43+00:00.

All the great vim plugins can be configured using global g: variables and overwritten by buffer b: variables.

So I can decide as user to set the normal behavior in my vimrc and overwrite those with autocmd or filetype files.

Now, as lua makes everything better and viml is such a hard way to learn, every nvim plugin comes with its own lua table for filetypes in its own global setup. Point.

No way to make a decide by buffer how the plugin behaves. Maybe I want the plugin go to left for markdown files under a specific folder but for markdown files in another directory go right? So the owner has to implement a callback function for my specific request, instead of using the variable scopes..,,

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/effinsky on 2025-06-16 07:58:06+00:00.

I currently use a combo of lazygit the cmdline tool and github in the browser. I'd like to do it a bit more ergonomically, since well we do a lot of this stuff as engineers. I'd love some recommendations.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/_vim_enjoyer on 2025-06-15 22:54:50+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/SuirtuE on 2025-06-15 22:45:50+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/Business_Horror_3323 on 2025-06-15 22:03:12+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/siduck13 on 2025-06-15 12:52:32+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/neovim by /u/AutoModerator on 2025-06-15 01:00:54+00:00.

If you want your dotfiles reviewed, or just want to show off your awesome config, post a link and preferably a screenshot as a top comment.

Everyone else can read through the configurations and comment suggestions, ask questions, compliment, etc.

As always, please be civil. Constructive criticism is encouraged, but insulting will not be tolerated.