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
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug_report.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,13 @@ assignees: ''
9
9
10
10
<!-- Any bug report not following this template will be immediately closed. Thanks -->
11
11
12
+
## Before Reporting an Issue
13
+
- I have read the kickstart.nvim README.md.
14
+
- I have read the appropriate plugin's documentation.
15
+
- I have searched that this issue has not been reported before.
16
+
17
+
-[ ]**By checking this, I confirm that the above steps are completed. I understand leaving this unchecked will result in this report being closed immediately.**
18
+
12
19
## Describe the bug
13
20
<!-- A clear and concise description of what the bug is. -->
14
21
@@ -18,8 +25,8 @@ assignees: ''
18
25
19
26
## Desktop
20
27
<!-- please complete the following information. -->
21
-
- OS:
22
-
- Terminal:
28
+
- OS:
29
+
- Terminal:
23
30
24
31
## Neovim Version
25
32
<!-- Output of running `:version` from inside of neovim. -->
You likely want to remove `lazy-lock.json` from your fork's `.gitignore` file
51
+
too - it's ignored in the kickstart repo to make maintenance easier, but it's
52
+
[recommended to track it in version control](https://lazy.folke.io/usage/lockfile).
53
+
54
+
#### Clone kickstart.nvim
55
+
> **NOTE**
56
+
> If following the recommended step above (i.e., forking the repo), replace
57
+
> `nvim-lua` with `<your_github_username>` in the commands below
58
+
59
+
<details><summary> Linux and Mac </summary>
41
60
42
61
- on Linux and Mac
43
62
```sh
@@ -63,15 +82,18 @@ Start Neovim
63
82
nvim
64
83
```
65
84
66
-
The `Lazy` plugin manager will start automatically on the first run and install the configured plugins - as can be seen in the introduction video. After the installation is complete you can press `q` to close the `Lazy` UI and **you are ready to go**! Next time you run nvim `Lazy` will no longer show up.
85
+
That's it! Lazy will install all the plugins you have. Use `:Lazy` to view
86
+
the current plugin status. Hit `q` to close the window.
87
+
88
+
#### Read The Friendly Documentation
67
89
68
90
Read through the `init.lua` file in your configuration folder for more
69
91
information about extending and exploring Neovim. That also includes
70
92
examples of adding popularly requested plugins.
71
93
72
-
```sh
73
-
nvim --headless "+Lazy! sync" +qa
74
-
```
94
+
> [!NOTE]
95
+
> For more information about a particular plugin check its repository's documentation.
96
+
75
97
76
98
### Getting Started
77
99
@@ -84,10 +106,10 @@ Each PR, especially those which increase the line count, should have a descripti
84
106
85
107
### FAQ
86
108
87
-
* What should I do if I already have a pre-existing neovim configuration?
88
-
* You should back it up, then delete all files associated with it.
89
-
* This includes your existing init.lua and the neovim files in `~/.local` which can be deleted with `rm -rf ~/.local/share/nvim/`
90
-
* You may also want to look at the [migration guide for lazy.nvim](https://github.com/folke/lazy.nvim#-migration-guide)
109
+
* What should I do if I already have a pre-existing Neovim configuration?
110
+
* You should back it up and then delete all associated files.
111
+
* This includes your existing init.lua and the Neovim files in `~/.local`
112
+
which can be deleted with `rm -rf ~/.local/share/nvim/`
91
113
* Can I keep my existing configuration in parallel to kickstart?
92
114
* Yes! You can use [NVIM_APPNAME](https://neovim.io/doc/user/starting.html#%24NVIM_APPNAME)`=nvim-NAME` to maintain multiple configurations. For example you can install the kickstart configuration in `~/.config/nvim-kickstart` and create an alias:
93
115
```
@@ -100,7 +122,7 @@ Each PR, especially those which increase the line count, should have a descripti
100
122
* The main purpose of kickstart is to serve as a teaching tool and a reference
101
123
configuration that someone can easily `git clone` as a basis for their own.
102
124
As you progress in learning Neovim and Lua, you might consider splitting `init.lua`
103
-
into smaller parts. A fork of kickstart that does this while maintaining the exact
125
+
into smaller parts. A fork of kickstart that does this while maintaining the
0 commit comments