Skip to content

Commit d69e20c

Browse files
committed
Update intstructions for existing nvim setups (nvim-lua#65)
* Update intstructions for existing nvim setups If you already had a nvim setup, then this makes it so that the kickstarter can work without a problem. Having that file exist and loaded with plugins gives the script many issues. Also better to have it be a shell command rather than have the script delete a bunch of files on your computer.
1 parent 8e242ba commit d69e20c

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,7 @@ This repo is meant to be used as a starting point for a user's own configuration
1818
* Start Neovim (`nvim`) and run `:PackerInstall` - ignore any error message about missing plugins, `:PackerInstall` will fix that shortly
1919
* Restart Neovim
2020

21+
2122
If there are languages that you don't want to use, remove their configuration and notes from your `init.lua` after copy and pasting (for example, in the mason configuration).
2223

2324
### Configuration
@@ -60,3 +61,9 @@ Pull-requests are welcome. The goal of this repo is not to create a Neovim confi
6061
* Lazy-loading. Kickstart.nvim should start within 40 ms on modern hardware. Please profile and contribute to upstream plugins to optimize startup time instead.
6162

6263
Each PR, especially those which increase the line count, should have a description as to why the PR is necessary.
64+
65+
### FAQ
66+
67+
* What should I do if I already have a pre-existing neovim configuration?
68+
* You should back it up, then delete all files associated with it. This includes your existing init.lua and the neovim files in .local which can be deleted with `rm -rf ~/.local/share/nvim/`
69+

0 commit comments

Comments
 (0)