Neovim with init.lua is faster

Open
#388 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
lua, neovim

Research direction

Start by reviewing how Vim and Neovim configurations are generated and whether the existing Neovim path can emit init.lua. The issue names no repository files or tests; compare the requested Lua configuration with its packer and impatient.nvim references. Done is not defined beyond a faster Neovim configuration, so scope and validation need clarification.

Written by the indexing model from the issue text.

Description

We all know how hard it would be to create a separate neovim exclusive config, but the speed it brings is huge.
Neovim now has native Language Server support, treesiter for better syntax.

There is a thread on Reddit on how much faster/or better using init.lua could be:
https://www.reddit.com/r/neovim/comments/jfs5sb/initvim_to_initlua_any_advantages/

Personally, I am using a plugin that caches lua plugins, which already are faster than pure vim:

    use {'lewis6991/impatient.nvim', rocks = 'mpack'}   -- faster startup

The plugin manager is packer (written in lua)

Even it took a long time to implement, this solution would be great

Dominant language
HTML
Stars
2.1k
Forks
208
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from editor-bootstrap/vim-bootstrap

All issues in editor-bootstrap/vim-bootstrap

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.