You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Make init.lua copy-paste friendly
* docs: Update README.md 📚
* correct typo
Hey y'all 👋
I think there may have been a typo?
* Remove timeout
* Add hint to uncomment line to autodetect plugins
* Remove fixed line number and describe line
* setup more language servers i use + allow customizing filetypes
* Fix bug when server not explicitely defined in configuration but installed
* Fix typo in init.lua
releated -> related
* fix(init): turn telescope-fzf-native into a dependecy
* fix: fix brackets
* fix: missing comma
* Update init.lua
added a URL to the lua-guide
may help others who miss the :help lua-guide
* Fix typo in README.md
* Use telescope for goto implementation
* Update init.lua
Fix typo in original.
Co-authored-by: Luis G Estrades <[email protected]>
* Revert gitsigns keymaps but fix vimdiff and fugitive conflict
Originally, the keymaps for jumping to next and previous git hunks were
]c and [c. This was changed in nvim-lua#323 (83b65a1) because they overwrote the
built-in vimdiff keymaps.
However, the more traditional solution is to have ]c and [c *extend* the
built-in keymap. This is what fugitive and gitgutter have been doing for
years.
Gitsigns doesn't do this by itself, but it has a recommended keymap
configuration on which the present patch is based:
https://github.com/lewis6991/gitsigns.nvim#keymaps
The only thing I've added is to have the keymaps work in visual mode as
well, which is the same behavior as the built in vimdiff keymaps.
* treesitter: ensure 'javascript' installed along with typescript and tsx
This parser is actually needed for some *JSX* parsing, and since
typescript and tsx are already getting installed, it makes sense to
also install the javascript parser.
* Add telescope search resume key binding
* docs: restructure README
* docs: remove archive installation
---------
Co-authored-by: Dheepak Krishnamurthy <[email protected]>
Co-authored-by: Andres Lowrie <[email protected]>
Co-authored-by: Chris Patti <[email protected]>
Co-authored-by: Andrew Stewart <[email protected]>
Co-authored-by: Dennis-Rall <[email protected]>
Co-authored-by: Numkil <[email protected]>
Co-authored-by: Ikko Eltociear Ashimine <[email protected]>
Co-authored-by: Peter Benjamin <[email protected]>
Co-authored-by: daan <[email protected]>
Co-authored-by: Smig <[email protected]>
Co-authored-by: Erik <[email protected]>
Co-authored-by: E. Aakash <[email protected]>
Co-authored-by: Luis G Estrades <[email protected]>
Co-authored-by: George Angelopoulos <[email protected]>
Co-authored-by: Dilshod Temirkhodjaev <[email protected]>
Co-authored-by: Luca Saccarola <[email protected]>
@@ -9,7 +11,7 @@ A starting point for Neovim that is:
9
11
* Documented
10
12
* Modular
11
13
12
-
This repo is meant to be used as by **YOU** to begin your Neovim journey; remove the things you don't use and add what you miss.
14
+
This repo is meant to be used by **YOU** to begin your Neovim journey; remove the things you don't use and add what you miss.
13
15
14
16
Kickstart.nvim targets *only* the latest ['stable'](https://github.com/neovim/neovim/releases/tag/stable) and latest ['nightly'](https://github.com/neovim/neovim/releases/tag/nightly) of Neovim. If you are experiencing issues, please make sure you have the latest versions.
15
17
@@ -18,42 +20,52 @@ Distribution Alternatives:
18
20
19
21
### Installation
20
22
21
-
* Backup your previous configuration (if any exists)
23
+
> **NOTE**
24
+
> [Backup](#FAQ) your previous configuration (if any exists)
25
+
26
+
Requirements:
27
+
* Make sure to review the readmes of the plugins if you are experiencing errors. In particular:
28
+
*[ripgrep](https://github.com/BurntSushi/ripgrep#installation) is required for multiple [telescope](https://github.com/nvim-telescope/telescope.nvim#suggested-dependencies) pickers.
29
+
* See [Windows Installation](#Windows-Installation) if you have trouble with `telescope-fzf-native`
30
+
31
+
Neovim's configurations are located under the following paths, depending on your OS:
22
32
23
-
### Archive Installation
24
-
* On the home/landing page for the project find the blue "<> CODE" button click it and select Local > Download ZIP.
25
-
* Extract the archive to:
26
-
`~/.config/nvim` (Linux)
27
-
`~/.config/nvim` (MacOS)
28
-
`%userprofile%\AppData\Local\nvim\` (Windows)
29
-
* Ensure your extraction method did not extract with a parent folder. For example in ~/.config/nvim you should have init.lua not another folder called kickstart.nvim.
33
+
| OS | PATH |
34
+
| :- | :--- |
35
+
| Linux |`$XDG_CONFIG_HOME/nvim`, `~/.config/nvim`|
* Run Neovim (from terminal or shortcut) and allow lazy.nvim to download files and set up the basics.
39
-
* Once the setup is complete, restart Neovim.
40
-
***You're ready to go!**
56
+
### Recommended Steps
41
57
42
-
* (Recommended/Optional) Fork this repo (so that you have your own copy that you can modify).
43
-
* Clone the kickstart repo into `$HOME/.config/nvim/` (Linux/Mac) or `%userprofile%\AppData\Local\nvim\` (Windows)
44
-
* If you don't want to include it as a git repo, you can just clone it and then move the files to this location
58
+
[Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) this repo (so that you have your own copy that you can modify) and then installing you can install to your machine using the methods above.
45
59
46
-
Additional system requirements:
47
-
- Make sure to review the readmes of the plugins if you are experiencing errors. In particular:
48
-
-[ripgrep](https://github.com/BurntSushi/ripgrep#installation) is required for multiple [telescope](https://github.com/nvim-telescope/telescope.nvim#suggested-dependencies) pickers.
49
-
- See [Windows Installation](#Windows-Installation) if you have trouble with `telescope-fzf-native`
60
+
> **NOTE**
61
+
> Your fork's url will be something like this: `https://github.com/<your_github_username>/kickstart.nvim.git`
50
62
51
63
### Configuration And Extension
52
64
53
65
* Inside of your copy, feel free to modify any file you like! It's your copy!
54
66
* Feel free to change any of the default options in `init.lua` to better suit your needs.
55
67
* For adding plugins, there are 3 primary options:
56
-
* Add new configuration in `lua/custom/plugins/*` files, which will be auto sourced using `lazy.nvim`
68
+
* Add new configuration in `lua/custom/plugins/*` files, which will be auto sourced using `lazy.nvim` (uncomment the line importing the `custom/plugins` directory in the `init.lua` file to enable this)
57
69
* Modify `init.lua` with additional plugins.
58
70
* Include the `lua/kickstart/plugins/*` files in your configuration.
0 commit comments