Neovim Pack

https://neovim.io/doc/user/pack.html#vim.pack

by k2enemy • 11 months ago

310 174 11 months ago

bikeshaving2• 11 months ago

I feel like I have to migrate to a new (Neo)Vim package manager about once every 3 or so years. I think my path has been: pathogen -> Vundle -> vim-plug -> lazy.nvim. Hopefully, this the last VIM package manager?

trip-zip• 11 months ago

Plug still gets the job done imo. But I'm also hopeful that since this one is builtin to the language it'll likely be end-game worthy for lots of users. I have tried it out and had a painless experience though I never did anything fancy like lazy offered.

jauntywundrkind• 11 months ago

Lazy.nvim seems pretty triumphant. But yeah a lot of others are also supported by various plugins. Some unity would be nice, abstractly. But man, it's hard to have faith we're going to get as anything good fast and reliable as lazy.nvim. it could happen though!

Lio• 11 months ago

Every plugin manager I've used since Pathogen has seemed "triumphant" at the time. I think they've all been reliable enough and everytime I think well this will be the last time I change that.

I currently have a Packer config on one machine and Lazy on another and honestly don't know why I bothered switching to Lazy. What I really crave is simplicity so if NeoVim builds every thing in I think it will be good enough for me.

f311a2• 11 months ago

New package manager is pretty slow right now, it's like 200ms to load nvim with lazy vim vs 1 sec with Pack.

christophilus2• 11 months ago

How many plugins do you have?

yoyohello134• 11 months ago

Luckily this is the built in, official, blessed one. So it’s likely going to be the most widely supported and available. (Maybe not most feature rich though)

film42• 11 months ago

I think I update Vundle like once every 3 years.

rapind2• 11 months ago

I’m literally just using git with vim.

gitaarik6• 11 months ago

How do you keep your plugins up to date?

leephillips• 11 months ago

Me too. I don’t understand why people think they need plugin managers. I just git clone the plugin into blah/blah/start and if I feel like updating one I do a git pull.

0x4572• 11 months ago

I started using nixvim. I think I gave up around vim-plug. Trying to maintain reliably working config across multiple machines and OS was a nightmare.

colordrops• 11 months ago

Nixvim is great. I got it configured with a flake and add it to all my machines. Nix lang is really suitable to composing neovim config.

schonfinkel• 11 months ago

I've been using the "old school" approach of just leveraging neovim + huge list of `vimPlugins` in my Nix config, makes you about the myriad of package managers for vim/neovim.

Replacing it with nixvim is on my forever growing todo list.

naniwaduni• 11 months ago

I tossed pathogen in favor of git submodules in ~/.vim/pack/*/start/ in 2017 and it's still like that.

rand0m4r• 11 months ago

same here - works great and never needed anything else.

sbinnee3• 11 months ago

I have been staying on vim-plug where everyone seems to be moving on to lazy.vim. I was considering a weekend to migrate to lazy.vim sometime. But with this news, I might just have to wait for this plugin manager to drop.

ComputerGuru• 11 months ago

Why? I’ve been using dein since it was released and haven’t needed to switch to anything (though I’ve noticed the momentum shifts quickly between different ones).

lawn2• 11 months ago

This is the FOMO speaking. You don't have to switch if you don't want to.

bravetraveler• 11 months ago

+1. Configured my plugins years ago and have not cared about the mechanism at all. I might even have confused things and landed on two. Whatever. The result is what matters: I have extensions.

In the exceedingly-rare event I do want to add one... overwhelmed with choice. "Have to" is entirely self-imposed

Aissen• 11 months ago

Just looked at my (private) dotfiles git history

- pathogen in 2011

- vundle in 2013

- vim-plug in 2017

Haven't moved since, Plug still does the job, even after I moved to neovim in 2021. Will probably move to the new built-in package manager once the dust has settled.

motiejus• 11 months ago

in Nix it's the same for as long as I remember, both on NixOS and nix-managed home-manager on MacOS and Linux:

      neovim = {
        enable = true;
        vimAlias = true;
        vimdiffAlias = true;
        defaultEditor = true;
        plugins = [
          pkgs.vimPlugins.fugitive
          pkgs.vimPlugins.fzf-vim
          pkgs.vimPlugins.vim-gh-line
          pkgs.vimPlugins.vim-gutentags
          pkgs.vimPlugins.nvim-lspconfig
          pkgs.pkgs-unstable.vimPlugins.vim-go
          pkgs.pkgs-unstable.vimPlugins.zig-vim
        ];
        extraConfig = builtins.readFile ./vimrc;
        extraLuaConfig = builtins.readFile (pkgs.replaceVars ./dev.lua {
              inherit (pkgs) ripgrep;
            }).outPath;
      }

burnt-resistor• 11 months ago

Similar here too. I'm on the lazy.nvim train too because it's componentized, powerful, and scalable. It would take me ages to get all of the stuff going that Just Works™ (pretty much) OOTB. Yes, even Copilot if you're into that sort of kinky code completion sharing with OpenAI/Microsoft everything you type.

azemetre7• 11 months ago

I recently moved away from lazy.nvim to using vim.pack. You can check out my PR here:

https://github.com/azemetre/dotfiles/pull/61/files

It was worth it to me because I never relied on many features of lazy.nvim. The benefit of the approach linked in the PR is that it also defer's loading packages as well. The only one I initially load is alpha.nvim (a dashboard), everything else gets deferred. This brought down my startup time from around 300ms to sub 100ms.

theflyinghorse• 11 months ago

You're using an editor that is built to be configurable for people who enjoy endless configuration. This will not be the last config manager. You might as well ask JS community if Nextjs is the last JS framework

amelius• 11 months ago

Yeah, this is like asking if "uv" will be the last package manager for Python.

dismalaf• 11 months ago

I'm torn. I really like Lazy and have never minded having different package managers for Vim over the years. But having one blessed one is probably better long term, just like built-in LSP and Treesitter.

shmerl6• 11 months ago

I agree if it at least can match lazy.nvim in features, which it so far doesn't. Stuff like pinning plugin versions, notifying about breaking changes and actual lazy loading are very useful.

3836293648• 11 months ago

It feels a bit dishonest to criticise an unreleased development build for a lack of features

porridgeraisin3• 11 months ago

It has pinning already

Freeze plugin from being updated:
- Update 'init.lua' for plugin to have version set to current commit hash. You can get it by running vim.pack.update({ 'plugin-name' }) and yanking the word describing current state (looks like abc12345).
- :restart.

azemetre7• 11 months ago

I recently migrated from lazy.nvim to vim.pack and it was way easier than expected:

https://github.com/azemetre/dotfiles/pull/61/files

I followed the work of another neovimmer where he was able to replicate deferring with vim.pack. Brought my startup time down to sub 100ms.

Definitely worth it to me as it's one less "core" plugin to maintain. Having things like telescope or trouble are one thing, it's quite another to rely on a plugin that changes the way neovim interacts with loading.

sbinnee3• 11 months ago

Does anyone know what’s the ground they want to make a builtin plugin manager? Did they think there should be some sort of standard?

bbkane2• 11 months ago

They're trying to improve "setup experience" - see https://m.youtube.com/watch?v=Nq2T28_ILxc (I forget the timestamp and exact phrasing)

yoyohello134• 11 months ago

The new LSP api is actually great. Makes the whole setup way easier. They’re really doing great work.

sbinnee3• 11 months ago

Thanks for sharing

qudat3• 11 months ago

A neovim plugin manager is essentially a git clone tool that knows how to execute a setup function. This aspect of plugin management is the same for all plugin managers in neovim. The goal is to have something that mostly works as-is but other plugins managers can potentially build off of to support advanced features like lazy loading.

TheRoque3• 11 months ago

I find it weird to not have one, given the ubiquity of plugins in (neo)vim. These editor are self-proclaimed "super easy to extend/program", until now it was awkward to need a third party plugin manager to "extend" them (the vast majority of people use plugins and don't extend all the functionalities with their own code). Plus 0.12 is said to be "The year of Nvim OOTB": https://neovim.io/roadmap/

pynappo• 11 months ago

Problem: New users must look for a plugin manager and figure out how to install it. - Nvim documentation should be able to give a one-liner to install (non-builtin) plugin managers and plugins. > Lack of a declarative way to specify plugins. - Lets Nvim reason about dependency ordering / transitivity. - Lets crawlers build a package index. - [packspec](https://github.com/neovim/packspec) adds potential to leverage NPM tooling (and possibly infrastructure).

https://github.com/neovim/neovim/issues/20893#issuecomment-1...

shmerl6• 11 months ago

Neat, but it's missing ability to lazy load plugins. I'm using lazy.nvim which is both lazy loader and update manager and it's really great.

robinsonrc• 11 months ago

Depending on the number of plugins you have, you may not notice the difference in practice. I certainly don’t but I’m very much on the minimal side of things. This all said I’m definitely of the school of thought that plugin developers should be responsible for ensuring their plugins are lazy loaded, rather than leaving it up to the user, who is not as well placed to make the decision.

shmerl6• 11 months ago

Well, it might work for individual plugins, but it can't work for when you use plugins as extensions for other plugins. How would plugin A know it has to load B (which is an extension of A) as a prerequisite for [lazy] loading itself?

Basically, only plugin manager can have a sane graph of plugins dependencies and know how to load them because that graph is in the end defined by the user (for the plugin manager) and plugins themselves have no clue what user might want.

azemetre7• 11 months ago

On the neovim subreddit one of the core maintainers said that relying on users to lazy load plugins is an extremely poor practice and something that should be done by the author's of said plugins. It is just a matter of how you initialize your plugin/name-of-plugin.lua file.

Don't know if it helps but I recently migrated to vim.pack. With another neovimmer he helped me create a defer function and pack update. The only plugin I initially load is a dashboard while deferring everything else. Brought my startup time to sub 100ms.

https://github.com/azemetre/dotfiles/pull/61/files

shmerl6• 11 months ago

I don't understand that argument (and I've heard it several times), see comment below about plugins dependencies. I.e. that argument is OK for isolated cases, not for more complex dependency graph.

CGamesPlay4• 11 months ago

This is the original issue that added this: https://github.com/neovim/neovim/issues/20893

Apparently this has been a long-time goal of the Neovim project, but it isn't really explained why. It feels like bloat in a space where existing plugins did a fantastic job, but apparently some people disagreed with that.

justinmk2• 11 months ago

It is explained in that issue: https://github.com/neovim/neovim/issues/20893#issuecomment-1...

CGamesPlay4• 11 months ago

@justinmk, thanks for all your work and leadership on neovim. I'm not excited about this feature, but in general I am excited about the changes I've seen in the project. Making a text editor is definitely not my life's ambition, but I'm glad you're taking up the challenge.

...

I don't really agree that "New users must look for a plugin manager and figure out how to install it". The only users who need to do that are the ones who have already found a plugin that they want to install, and which also doesn't provide installation instructions of its own. I don't agree that "Lack of a declarative way to specify plugins" is a valid problem, since this problem is actually introduced by bundling a plugin manager.

And this justification for creating the feature completely ignores the several high-quality existing, unbundled implementations of plugin managers. The installation of Lazy.nvim is entirely within your nvim init files, demonstrating that 3rd-party plugin managers can have simple installation instructions.

The bundled package manager also makes some trade-offs that 3rd-party ones don't have to make (e.g. support for non-git plugins). This is addressable, like the lack of lockfiles, automatic dependency management, and re-implementing every other feature that existing plugins already provide. That's why this is bloat. This task is better-served outside of the core project.

higon• 11 months ago

Still primitive. But I'd love to drop lazy for this once they implement a differed load.

I love lazy.nvim. It's great no doubt. But recently I felt like the author is taking an aggressive user retention behavior by re-imprementing every useful open-source community plugins out there (like snack.nvim, mini.nvim). That's a kill-zone/copycat strategy. I don't get it.

aldanor• 11 months ago

And then ditching those packages unmaintained (like snacks).

// mini.nvim is a completely different author though and doesn't have to do much with lazy

dannyfritz072• 11 months ago

I believe folkes is just on vacation. Hardly ditched.

johnnypangs• 11 months ago

The mini.nvim maintainer is the one who did a lot of the work for pack I believe:

https://github.com/neovim/neovim/pulls?q=is%3Apr+pack+is%3Ac...

kzrdude6• 11 months ago

I think he's pretty well placed to implent good interfaces following his paradigm, noticeably different than some other authors. I like it, so I often think his take is the best.

Snacks picker is now the best picker, for example.

wwarner• 11 months ago

M-x package-list-packages :)

sevensor• 11 months ago

You joke, but a colleague tried to get me using nvim a few months ago, and after installing all the stuff he recommended, my first impression was that I was running emacs. It was busy, there were extra buffers all over the place, things kept popping up as I typed, and I wasn’t clear on how to get to normal mode. In sure this has as much to do with his config, which I copied without understanding it, as it does with nvim itself, but it felt very unfamiliar.

lenkite• 11 months ago

and I wasn’t clear on how to get to normal mode.

You need to ditch your heretical friend if he has broken the Holy Commandment of <Esc> to get to Normal mode.

qudat3• 11 months ago

I’ve been using it for awhile, no issues: https://erock-git-dotfiles.pgs.sh/tree/main/item/dot_config/...

christophilus2• 11 months ago

That is a thing of beauty.

OJFord3• 11 months ago

I don't need this to be minimal, I'd love it to be the one true solution, niche requirements excepted.

I'm currently still using vim pack with git submodules because I can't be bothered to trawl through tens of GitHub projects to work out what's the best supported / most liked / currently recommended third-party nvim package manager.

ordinaryradical• 11 months ago

Built a single file config with this after watching Sylvan Franklin and TJ DeVries a bit on YouTube and it has been great. Config junkies may need something more, but for a minimalist (and is minimalism not the essence of neovim?) it’s lovely.

geophph2• 11 months ago

Vimotheé!!

TheRoque3• 11 months ago

Discovered this guy recently while looking for a new vim.pack config. He's quite funny.

qudat3• 11 months ago

Link to src?

TheRoque3• 11 months ago

https://youtu.be/xGkL2N8w0H4?si=_U9rFhZM50Dg4cVw

mkhalil2• 11 months ago

Every time I see a something with the ability to import code from Git, especially if they allow specifying a branch (this pack even supports commit hashes), I wish they would document (and that more people would know) that they can "checkout" a branch at a specific time; because a lot of branches (vim plugins included) don't even bother with versioning.

ex: you can use this to checkout a repo @ a specific datetime: > git checkout 'master@{2025-05-26 18:30:00}'

just doing my share to help people steer away from another leftPad disaster (or the xz apocalypse that almost was...)

CGamesPlay4• 11 months ago

Why not by SHA?

Lermatroid• 11 months ago

Dates make pinning easier than looking up a SHA

bikeshaving2• 11 months ago

I’m curious. What’s the risk of a supply chain attack? What are the privileges of a VIM plugin?

feinte• 11 months ago

A plugin can spawn arbitrary processes so if neovim is not started in a sandbox (container, namespace, firejail...) they can basically do whatever your user has the right to do.

Pretty big supply chain risks here.

asimovDev• 11 months ago

neovim (vim) plugins can make web requests, so you could steal secrets from a .env file being edited by, for example, making a LSP plugin active for .env files? According to my limited knowledge of LSP and how neovim plugins work, it should be possible

Could also just phone home everything a user edits using the text editor I bet.

Can someone tell me, when someone has a terminal buffer, using a vim plugin, could you potentially steal their root password when a user runs a sudo command?

And following up, could you, using that password, allow SSH connections and open ports in other system config files? Disable firewall? And potentially execute other commands using `:!` ?

kzrdude6• 11 months ago

Anything a user application can do

manwe150• 11 months ago

I thought that gives master as of your pull time, not nearest commit to that time, which seems very confusing (it isn’t reproducible, except for yourself). I think you need a more complicated git log —before=time for any semblance of reproducibility

mkhalil2• 11 months ago

Good catch, you are correct. I initially was going post the actual command for checking out a branch at a time:

git checkout $(git rev-list -1 --before="YYYY-MM-DD" master)

but thought I found a shortcut - which turns out is not really one, and like you said: confusing.

I can't edit my post, but in any case; the point being: it would be nice if import statements are closer to "github.com/google/uuid@YYYY-MM-DD" or in this case you can pass a date to version: "YYYY-MM-DD" and the library would run the uglier nested command above to import the proper version.

xlii• 11 months ago

Seems like a plausible idea but working with clocks my first question would be "whose clock is it". Is it repository defined clock? My clock? Git remote’s clock?

AFAIK this can be used for hashes, but friends don’t let friends use clocks in software developments (unless it’s last resort).

Buttons840• 11 months ago

One step closer to having all the features of Emacs. :flex:

I love Vim key bindings, and I'm happy to see the flagship of Vim keybindings improve.

geophph2• 11 months ago

I’ve migrated over to it - got about 12 plugins or so. No complaints so far! I don’t have strong opinions on whether my plugins are loaded lazily or not. Seems to work fine to get it done and get out of the way.

babalark• 11 months ago

I'm really looking forward to this. I hope it helps push the nvim plugin community into lazy loading plugins by default instead of relying on a complex plugin manager like lazy. The nvim docs have a little note related to this[1].

I'm quite a fan of the nvim-neorocks plugin best practices as well[2]. In fact it seems like part of them got merged recently[3] hahaha.

[1] https://neovim.io/doc/user/lua-plugin.html#lua-plugin-lazy

[2] https://github.com/nvim-neorocks/nvim-best-practices

[3] https://github.com/neovim/neovim/pull/29073

WhyNotHugo3• 11 months ago

The neovim model of using setup() makes lazy loading a bit trickier than traditional Vim.

Lazy loading is much easier with Vim’s model of configuring by setting variables. You just set variables in init.vim, and the plugin can auto-load when one of its functions is executed.

With lua this requires more orchestration; if many autocmd refer to the same plugin, they all need to explicitly remember to call setup().

mrcjkb4• 11 months ago

Neovim provides the same mechanisms as Vim for Lua plugins. The problem (and part of my motivation for writing the nvim-best-practices document) is that not enough plugins use them.

Edit: The Neovim setup antipattern is the Lua equivalent of writing Vimscript functions in autoload and asking users to call them in their configs instead of doing so automatically.

kzrdude6• 11 months ago

The settings variable convention is not good, uses random variable prefixes. A new convention is needed, then the ball can start rolling on that. Until then the lazy nvim and/or setup paradigm is useful.

saint_yossarian2• 11 months ago

AFAIK using setup() is actually a cargo-cult practice and discouraged by the Neovim maintainers.

phplovesong• 11 months ago

Over the last decade i went thru 4 package managers. I always hoped for a builtin one. Over the years my package dep count has decresed radically. I think i use 4-6 plugins (and one theme) really on a daily basis. The rest is nice to haves i probably use once a month making them up for deletion.

justicehunter• 11 months ago

Plan to switch from vim-plug to this one, hopefully wont have to change again

porridgeraisin3• 11 months ago

I build neovim from source by myself, and maintain plugins as git submodules in pack/plugins/start (nvim automatically loads these at startup) and pack/plugins/opt (these are loaded manually) by myself. I have stuff like emmet, diffview.nvim, nvim-dap, etc loaded optionally when I want to use them. Status bar, LSP, Treesitter, and a few small tpope plugins are loaded on startup. I have a 500 line init.vim. I have a few local patches for some of the plugins.

This way, _nothing_ changes ever. That's how I want it.

I used to use astro.nvim (a few years back), then at one point I upgraded it and they had changed all the keybinds (even for basic shit like go to references IIRC), it was absolutely insane. I lost my shit and deleted the whole thing and moved to this setup. I will never use an nvim distro or update nvim plugins ever again. If I really want something I will git pull it myself (I'm looking out for nvim 12's ghost text feature for example). But in the general case, I'm done with any changes whatsoever. Not one byte.

I actually open-sourced my "approach" and documented it but I left it midway, if others are interested I might stop procrastinating and actually finish it.

vander_elst• 11 months ago

I like the approach! I'd be interested in reading more. I might not fully adopt it but I m on a similar wavelength about stability. I don't want things to change unexpectedly, I just want my tools to just work consistently without surprises.

dboon2• 11 months ago

It’s funny when you start a project and then find something so similar in the wild.

I’m writing a C package manager in exactly the same vein. Git based, no binaries, rolling release. It’s probably not such a coincidence, since I was inspired by Lazy in the first place.

https://github.com/tspader/spn

emigre• 11 months ago

Neovim is really excellent, it's so good that they are adding a package manager. Loving this.

xigoi2• 11 months ago

I’m disappointed that it requires the plugins to have a specific scheme for naming branches, so it won’t be compatible with all plugins.

GCUMstlyHarmls2• 11 months ago

Not sure what you mean by this. Do you mean for versioning requiring `vX.Y.Z` tags? That's quite standard (linux kernel does this). Otherwise it defaults to main/master branch which is also basically standard depending on when the repo was made...

xigoi2• 11 months ago

Do you mean for versioning requiring `vX.Y.Z` tags?

That, and also it has to be specifically Semantic Versioning.

WhyNotHugo3• 11 months ago

You don’t really need a Vim plugin manager, especially if you use git for your dotfiles.

Installing a plugin merely requires placing its files (eg: cloning its repository) into a well-known location. You can just do that.

If you track your config with git, you can track plugins with submodules. This has the added advantage of pinning the exact version (and tracking that version in for).

riedel• 11 months ago

I find myself enabling and disabling some plugins frequently and find it easy via the com config than the shell/filesystem . However, more importantly plugins can be activated easily based on file-type. Most plugin managers are anyway only a small wrapper around git, I guess.

setopt• 11 months ago

If you track your config with git, you can track plugins with submodules. This has the added advantage of pinning the exact version (and tracking that version in for).

I did this for a year or so, with the motivation that submodules could replace all tool-specific package managers (for vim, tmux, zsh, etc.).

But honestly managing Git submodules felt like a chore compared to my old `vim-plug` setup. Basically because submodules are a neat concept but not implemented very ergonomically in Git. Eventually I just went back.

If someone has a setup using built-in vim pack that feels more ergonomic than vim-plug et al. then I’m very interested to hear.

ho_schi• 11 months ago

Nice.

Should it provide to backup/install local plugins? I mean, probably I can move the directory with it into the correct destination.

commandersaki• 11 months ago

Seems like every 3 months something new supersedes the incumbent. I’ve been using kickstart.nvim and maintaining parity with all the changes has been chaotic.

saint_yossarian2• 11 months ago

Well kickstart.nvim is a template for your own configuration, not a distribution. You're not supposed to update it.

bpierre• 11 months ago

I recently migrated to it [1], no issues so far. It doesn’t have the many features Lazy.nvim has (e.g. lazy loading of plugins that can be triggered in various ways), but this is a tradeoff I am fine with.

[1] https://github.com/bpierre/dotfiles/blob/main/nvim/lua/packa...

lukaslalinsky• 11 months ago

I'm a long time vim user, but neovim with plugins is just not worth it for me. Something always breaks. I think neovim would do better if they started integrating the core plugins like LSP, tree sitter

normie3000• 11 months ago

Same, but I'm guessing it'll settle down in the next 5-10 years.

lawn2• 11 months ago

I think neovim would do better if they started integrating the core plugins like LSP, tree sitter

That's exactly what they're doing.

Both tree-sitter and LSP are built in and the primary LSP/tree-sitter plugins only bundle default LSP configurations and tree-sitter queries respectively. They're also planning to include tree-sitter query bundling into Neovim natively somehow, to make it even less reliant on the nvim-treesitter plugin.

They recently simplified the LSP configuration and to configure a new LSP you basically do this:

    vim.lsp.config("expert", {
      cmd = { "expert" },
      root_markers = { "mix.exs", ".git" },
      filetypes = { "elixir", "eelixir", "heex" },
    })

    vim.lsp.enable("expert")

And then in the "LspAttach" autocmd you can define your LSP specific keymaps for example.

GCUMstlyHarmls2• 11 months ago

And then in the "LspAttach" autocmd you can define your LSP specific keymaps for example.

If you want. It also now ships with most auto-mapped.

cassepipe• 11 months ago

I was the same and kept using vim for C/C++ development. vim-plug, gutentags (ctags manager), ALE did their job pretty well and I didn't bother to learn another way.

All that changed with web dev where you have to juggle with different syntaxes and tools... I decided I would just use a neovim distribution. I have tried many but Lunarvim (now inactive) and now Astronvim have served me well so far.

divan• 11 months ago

From the name I initially assumed that it's about adding 'packs' (maintained group of plugins) similar to AstroNVim community packs [1]

[1] https://github.com/AstroNvim/astrocommunity/tree/main/lua/as...

azemetre7• 11 months ago

If it helps any neovimmers I recently migrated away from lazy.nvim to just using vim.pack:

https://github.com/azemetre/dotfiles/pull/61/files

I have had zero issues thus far, also don't use too many plugins (like 50ish). It was way easier than expected, also had help from another person making the plugins load similarly to "lazy" as well. This setup is way way way faster than using lazy.nvim IME, especially my work computer where it would take 300 ms to load. Now it's around 80ms.

c-hendricks2• 11 months ago

You're linking this all over the place so heads up, it links to an unrelated file in the diff.

azemetre7• 11 months ago

My bad, updated the links now. Reason for the passion is that I originally found out about neovim on hackernews where someone shared their dotfiles setup that used vim-plug with neovim. It looked simple to transition and I did.

Just trying to share the love.

mvieira38• 11 months ago

Can't say I'm looking forward to migrating from lazy.nvim, tbh... Can anyone tell me what this does better than lazy? I can't really tell from the docs alone

synergy20• 11 months ago

More news on neovim than vim these days, including this one. I wonder if I should switch to neovim, as more AI related plugins are neovim only. In the meantime, Vim has served me fine so far.

a99c43f2d565504• 11 months ago

Offtopic, and no one asked, but I'm going to advertise anyway: Helix is a good alternative to (neo)vim for anyone who wants a terminal editor with vimotions(ish) but doesn't like configuring or scripting. That was the selling point that made me stay with it: The out-of-the-box experience was close enough to what I was hoping to end at but gave up with neovim due to the hassle required. It is opinionated of course, but the default behavior and appearance of Helix felt much more appropriate than that of neovim.

wredcoll• 11 months ago

Can I use wasd for my movement keys?

CollinEMac• 11 months ago

I'm a Neovim user but I have to agree with the recommendation. If you've wanted to check out vim/emacs but were nervous Helix is a good place to start.

I do wish there was at least the option to use vim keybindings in Helix though. The Helix keybindings are mostly the same but just different enough to be annoying if you're already used to vim.

Edit: typo

dannyfritz072• 11 months ago

I haven't used it, but I've seen people speak well about evil helix https://evil-helix.github.io/

xcrjm• 11 months ago

Someone else mentioned evil-helix if you really want those keybindings but, admittedly, I think the different keybindings (and more specifically the select then operate model) are a major point of why helix (and its inspiration, kakoune) exists.

tomku• 11 months ago

I actually like Helix a lot too, but it is different than (neo)vim in a lot of significant ways. It feels like alternate-universe vim more than just better defaults. It also doesn't just not require scripting, it doesn't support scripting (yet). Very interesting in its own right but it might not be what you want if you're familiar with (neo)vim already.

bbkane2• 11 months ago

I still have to interact with files on servers I don't control, so I still need to keep basic vim motions in my working set memory unfortunately

Gabriel54• 11 months ago

I've been very happy with Paq [1] which is essentially a lightweight wrapper around git pull.

[1] https://github.com/savq/paq-nvim

c-hendricks2• 11 months ago

Given how many configs being shared here which include their own half-baked (no offence!) `add_plugin` functions which replicate traditional vim plugin managers, there's definitely still room for something like Lazy which just wraps `vim.pack`

Neovim Pack

Related Stories