Add support for neovim init.lua configs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when I have to make changes to my .vimrc file (I set "vim.vimrc.enable": true) to reflect changes I've done in my init.lua file (when configuring nvim). P.s. I'm aware that there is a "vim.neovimUseConfigFile" option, but when I tried setting "vim.neovimConfigPath" to my init.lua, it didn't work (simply nothing happened), so I'm assuming it only works for init.vim, which is very unfortunate
Describe the solution you'd like
Add support for init.lua, same as there currently is support for .vimrc (and init.vim, which I haven't tried, but looks like it's there)
Describe alternatives you've considered
Make neovim use the same configuration normal nvim would (init.lua) when "vim.enableNeovim" is set to true. This would actually be ideal
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the vim.vimrc.enable, vim.neovimUseConfigFile, and vim.neovimConfigPath options, then compare how init.vim is handled with the requested init.lua path. Done means Neovim can use init.lua without duplicating settings in .vimrc, with the existing configuration behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- neovim, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100