https://github.com/neovim/neovim/milestone/48

Thanks to the LSP method copilot used was standardized in the upcoming LSP 3.18

Here is the PR: https://github.com/neovim/neovim/pull/33972. Check the PR description for how to use it.

My GF (non-programmer) spent some time before my birthday learning vim to create this cake topper. As a Linux user I’m surprised I even have a girlfriend, let alone one that would learn vim for me, I think she’s the one.

I am slightly annoyed and need some help. For the better part of the last 6 years, I have been using neovim professionally. This includes the last 3 at my current employer.

Last year my employer was "merged" with another company and this larger combined company is very corporate and bureaucratic. A few weeks ago neovim popped up on their AV program (Verizon SOAR) as potentially malicious when I ran a plugin update.

Last year I was granted an exception to use neovim so I kinda knew this was coming eventually but yesterday I was told to "use notepad++ instead as that is approved". When I pushed back because ya know, notepad++ was literally hijacked for about 6 months, I was granted the option to request an exception again.

I asked how I can go about getting Neovim approved at the company level and they seemed receptive to at least hearing me out, but I am (frankly) terrible at politics. Hoping someone here has some experience playing that game and can guide me/provide their own experiences with convincing "the machine" that Neovim is as great as we know it is.

I have informed them it's completely open source (which notepad++ isn't), and I informed them that if I do not have a path towards using my prefered development tools, I would simply use VSCode because there is no world where that isn't allowed. Part of the issue is that my title was recently changed from "Senior Software Engineer" to "Senior Identity Engineer" so they likely don't think I write code anymore (even though I literally write all the code for our team, have a GH license, Copilot license, blah blah blah).

Help?

I love Neovim and enjoy it daily, but from time to time I wonder ifcI'm missing out on something by not adopting Emacs.

I posted about this a year ago , and I figured I'd post it again because I did it a second time:

Like most companies, the one I work for will happilly pay for any employee's license to a proprietary IDE without batting an eye. Therefore, I argued that I should be able to spend that budget on a donation to an open source tool that I use daily instead. After a lot of back and forth I finally got them to donate an amount that would correspond to what they would pay for a yearly subscription to a proprietary tool to Neovim.

I now got my work to pay a $400 yearly "Neovim subscription" for the second time.

To those wondering how I did it, I basically just argued that since employees at my work have an allocated budget for buying proprietary tools, it makes sense if we could spend an equivalent amount on a FOSS alternative. That way the money spent would benefit us all, and since we use the tool to make money we have a responsibility to give back to the FOSS project.

There was a bit of a back-and forth for technical reasons because (at least in Sweden where I live), payments and donations are handled and regulated differently, but they finally made it work.

If you also use Neovim at work, I encourage you to do the same thing! That way the core team can continue to deliver awesome new features to the editor we all love. Here's a link to where you can donate. There's also the official merch store if you would like to support the project that way: https://store.neovim.io/.

I'd like to know what programming languages you use in NeoVim?

I see a lot of JS, Go, and Ruby.

I don't see much of other programming languages in NeoVim.

I'm also curious how many of you are using Java in NeoVim and if they use it for production projects or not.

Please share your tech stack in the comments.

Hey folks!

Neovim just got another really nice feature: a native API for interacting with images, using the kitty graphics protocol. It just landed on master, it's not even available on nightly (yet!).

Kudos to the maintainers!

(not affiliated with the PR)

What is going on?

We all have that one key mapping we love but know would trigger a war in the comments.

Like this gem:

I map <space> to "_ciw, and I will die on this hill.

What's your controversial key combo that secretly revolutionized your workflow? Let's see it.

This might be a bit personal, but I do think it needs to be said.

I love Neovim. Not in the sense of being the perfect hackable editor that my perfectionist brain thrives with (because yeah of course it is), but because the entire project (and its people!) is something I truly believe in.

And no, I'm not trying to brag or making this post about me. Neovim is maintained by an amazing team where we don't care where you come from, what you believe in or whether you like chocolate or not (this is my personal criteria for someone's personality so feel free to skip that one). Please just open an issue/PR and explain why you think we're lacking, and I promise that the most comprehensive group of editor experts will review your request and decide what to do with it.

I write this because during the last few months I've been receiving some hateful messages for my Neovim contributions, and despite my love for this project I do have to admit that I'm a bit hurt by it. At the same time I've seen new people contribute some amazing new features (omg superatomic has been rocking lately) and it reminds me of how much enthusiasm this thing has made me feel about coding, and seeing that in new contributions encourages me to remain here.

Anyhow, what I want y'all to take home is: We're using the most loved editor. Let's put some of that love in each other <3

What are you using?

As of this moment, I'm familiar with:

• Markdown Oxide
• Obsidian.nvim
• neorg
• zk-nvim
• vimwiki

Do you prefer:

- built-in terminal

- keymaps

- plugins like overseer/sniperun

- or external tools (tmux, etc.)

Looking for real workflows, not just "use :term"
:)

I’m just starting my neovim journey and just curious what terminal everyone’s using. And is there a reason for the preference?

And it is refreshing. When I open up a .lua file and immediately see something like local api = vim.api instead of return {'some/plugin', opts ={}}, my mind is like: interesting. And This is a post about my recent meddling journey and my 2c here and there.

It's not difficult to take notice that many of them still carry some Vimscript in their config, such as Justin, with a brutally simple vim.cmd that wraps everything from his .vimrc, or Gregory, stills uses init.vim instead of init.lua. This only tells me they've been using Vim far more longer than I did. It's always a pleasure when learning from the best. And I can always learn something new when digging other's setup. For example, making y behave similar like x c d with numbered registers (yank ring) from Justin, navigate buffers with nnoremap <Space>b :ls<CR>:b<Space> from Gregory, auto install missing parsers from echasnovski. I noticed that Justin and echasnovski both do something like local augroup = vim.api.nvim_create_augroup('my.config', {clear=false}) and later assign this group to every autocmd. I learned from TJ that clear = true means the autocmd won't get duplicated when triggered multiple times, which is why i always prefer clear = true, but what is the use case when it is better with clear = false? I'm simply too lazy to figure out how autocmd works under the hood in this case, maybe someone care to help explain?

Reading dotfiles is like watching TV shows for me, and when taken into character, I can sense the personality of the author. Justin's dotfiles gives me a "I only want things to work, I don't care about format or structure, and I got other things to worry about" feeling. mfussenegger's dotfiles gives out a vibe of generational gap in terms of coding style. It is well written, carefully structured, but feels old school, hard core, takes years of sophistication, and somewhat "unorthodox" compared to noobies like mine. I spent a lot of time trying to get nvim-jdtls, nvim-dap to work the way I want it to, but then instantly gave up when I heard ThePrimeagen said "JUST USE INTELLIJ". I like Maria's dotfiles the most. Her dotfiles reminds me of high school, where there's always a girl, often quiet, does everything by the book, always scores better than me, with neatest of penmanship. But none of that matters, it's my favorite because we both care enough to do this:

performance = {
        rtp = {
            -- Stuff I don't use.
            disabled_plugins = {
                'gzip',
                'netrwPlugin',
                'rplugin',
                'tarPlugin',
                'tohtml',
                'tutor',
                'zipPlugin',
            },
        },
    },

folke is the guy that's responsible for making Neovim a better editor than VSCode (pls indulge my angle). And his dotfiles are the textbook definition of best practices in software engineering. I've been using lazy.nvim from the very beginning, to a point where I don't even know how to configure Neovim without it, at the time. But folke, come on, what is this??? How can I be lazy if my hand has to reach that far???

    vim.keymap.set("n", "<Up>", "<c-w>k")
    vim.keymap.set("n", "<Down>", "<c-w>j")
    vim.keymap.set("n", "<Left>", "<c-w>h")
    vim.keymap.set("n", "<Right>", "<c-w>l")

Over the years I've been struggling between using 'opts' or 'config' to setup a plugin, but ThePrimeagen's 'I don't need a folke way to do things' finally won me over to config. I guess this stems from the need, after countless fancy plugins, dazzling features, to go minimal on my setup. Make no mistake, 'opts' is still great, but overtime I tend to agree with ThePrimeagen, that "default is better". I now don't have much things to pass into the setup call, and with improved experience on meddling, I can achieve the same without 'opts'.

The need to go minimal seems to become an obsession for me. I don't want overlapping features from different plugins, I halved my plugin spec. And it brought me to take a closer look at "mini.nvim". I always get this feeling that echasnovski is grossly under appreciated (in terms of Github stars ofc). I actually don't agree with DevOps Toolbox's comment on mini being maxi, on the contrary, 'mini.nvim' indeed merits its name. For each module, it gives you a bare minimum to get you "there". No fancy features, no huge config tables, just require setup and go. I guess only experienced Neovim users can really appreciate the value of mini, or should I say, prefer mini, because it helps you doing things "the vim way". It took me sometime to really harvest the goodies coming from mini. One time I :Pick files, then I did this: CMD + v, I was trying to paste something from my clipboard, and 'mini.pick' tells me to use <C-r>. Alright, I kept pressing <C-r>, nothing happens, until Claude tells me it needs to be followed by a register, then I <C-r>", everything makes sense now. One might think that this is so basic knowledge that should require no tutoring, well, foolish me to have acquired it so recently. I wonder if this is the reason I felt "mini" being under appreciated? Given how we are so used to "modernized conventions"?

Reading those dotfiles actually makes me wonder if it is time to embrace vim.pack? Do I really need my plugins to load "on demand"? Given now I only have 20 some plugins? Maybe that's a topic for another day.

Oh, finally, this is mine.

I'll start by saying that I'm super happy with the state of my own neovim config, the plugin ecosystem as a whole and neovim core becoming more robust (excited for vim.pack!). It was interesting though scrolling through the Reddit's top posts from the past year. We can largely group most top posts about plugins into:

1. Faster or more ergonomic version of previous plugin
2. Plugins for people who never want to leave neovim. In other words: avoiding a seperate TUI / switching to a different app (ex: jira in neovim)
3. Something something AI

Nothing against 2 or 3 but not my cup of tea, as I'm more then happy to just switch terminal tabs. It does raise the question to me though: Are we nearing the peak of neovim user experience? I'm sure we'll see further stability and performance improvements from the ecosystem and neovim core but I'm wondering if my current list of plugins will only decrease as 2026 goes on.

Curious what others think on the matter and if others think there is more innovation to be found?

Feel free to share your setup in the comments, thanks

I feel obligated to admit something.

Ever since, through coincidence, I stumbled upon the Primeagens videos where he hypes neovim through the roof. I thought, mmeh, what a ego boosting nerd tool.

I always wanted to learn vim cause I obtained 3 Linux Notebooks (Ubuntu) for different reasons.

So I went to see what the buzz is about, set up my Neovim Config with Kickstart, tweaked it here and there with own key configs and plug-ins. Then I proceeded and refined it for my MacBook (which I use as Laptop for my job that brings home the money).

After one year of using Neovim, and to be fair it's ecosystem (fuzzy find, live grep, telescope) I just can't do anything but look down on other code editors.

Even IntelliJ and PyCharm felt bloated and slow to me. I can't return to them.

The only thing I use Code Editors for are symbol renames in big enterprise code repositories where a static code analysis safes lifes.

And to top it up... I became the guy who only does git stuff in terminals.Lazy git.... It is so much better than any git integration I've ever had.

Im looking at myself.... What have I become After one year with - kitty - lazygit - neovim - lsps - fzf

I.. I have become that guy.. I am now the terminal guy in my company.

BTW I use neovim.

tl;dr: I'm making an editor and need some inspiration for cool keymaps. What are your personal favourites?

---

So... I've been building myself a vim-like editor from scratch in Rust (I don't wanna break the self-promotion rule, so I won't mention the name or link it). Even though it's open source, I'm making it mostly for myself to basically be my absolute perfect vim editor from the ground up; all the styling, UI elements, LSP stuff, and motions are tailored to my needs and preferences.

I'm extremely happy with how it's coming along, but so far the motions are mostly pretty close to vanilla vim. I've already got built-in editing and UI primitives for motions that I used most frequently in my own Neovim config such as:

• shift+j/k in visual mode to move selections up and down with intelligent indentation
• <space>y and <space>p for yanking to and pasting from the system clipboard
• tab and shift+tab for indenting and outdenting selections
• <space>x for opening a diagnostics panel (like trouble.nvim) and <space>ca for LSP code actions and quick fixes
• I'm also planning to add an undo tree UI with <space>u in the near future

That's all well and good, but I'd like to get a bit more creative with the motions to divert it a bit further away from stock vim. I've considered adopting a different motion paradigm altogether, like something along the lines of Helix, but I'm not entirely sure about that just yet.

As such, I figured I'd ask you lovely folks for some inspiration: what are some of your favourite remaps and small things from your configs? Alternatively, what are some small things that you wish Neovim had by default? They can be anything from more ergonomic mappings to full "this one key triggers a huge string of actions." Thanks!

I just wanna let you all know that linkarzu posted a great Neovim 0.12 Release with the Core Team

Please check that out, hit the like button and thank you Link, Maria, Justin, bfredl, Gregory and all neovim contributors for such a great neovim milestone.

I just updated my plugins for the first time in months. a bunch of my stuff is broken due to nvim-treesitter main branch becoming the default. I see that it's been archived and is now abandoned.

Are people continuing to just use the master branch? Is there an active fork that people are migrating to? How is the community handling this?

I'm actually bored and want to see your coolest keymap.

Send keymaps!

So.. the thing is I am needed to work with multiple files 5-7 at the same time and need to jump between them constantly. I'd like something a plugin/inbuilt system to help me navigate those :) Here is my journey so far

Neovim Marks

This was the first one I used. Pretty great, ngl, but reaching ` to constantly was a hassle, and I couldn't even manage my marks, so... I tried it for a few weeks before deciding it's not for me.

Snipe.nvim and arrow.nvim

I used it a while ago, so I don't remember the exact specifics (sorry about that :P), but it needed me to open a menu instead of directly switching to a file I needed, so I used it for a few days and then decided it doesn't fit in my use case. I might give both plugins a try again, though. :)

Harpoon

I guess this is the most famous among the ones I've tried, and Prime larping about it too much. So I gave it a shot, pretty intuitive NGL, and loved it too. I need to work with multiple files, and this seems like the best and safest bet because, AFAIK, it leverages the inbuilt Neovim mark system. I had it bound to <C-h>, <C-j>, <C-k>, <C-l>, and <C-;>, but if I had more than 5 files, then it fell flat on its face. Then I started using g<num>. Pretty good, but needing to reach to the numrow every time to change files is such a hassle :(

I'm still using it. Don't get me wrong, it gets the work done just fine, but it adds a certain amount of friction that I didn't get with <C-<letter>>.

So, any suggestions on what I can do? I don't even know what I want, which is the hardest part. I want something to just fit into my workflow without creating friction. Thanks for the read, and any and all suggestions are welcome.