| Age | Commit message (Collapse) | Author |
|---|
|
"Getting Started"
|
|
Changing this second "Introduction" heading to "Getting Started"
The recent change in README which moved the youtube link from FAQ
to it's own section used the heading "Introduction" which is already
the first heading in the file.
|
|
|
|
To help new users get started, how about moving the video link ("Effective Neovim: Instant IDE ") right after "Post Installation"?
This way new users, can install it, and right away proceed to learn how to use it.
|
|
|
|
|
|
* Update README to reflect modular organization
- Change install links to this repo instead of nvim-lua/kickstart.nvim
- Change “Recommended Steps” repo link to reflect kickstart-modular.nvim.git
- Change FAQ re: multiple files to reflect that we are in the modular repo, not the single file repo.
|
|
|
|
It is much easier to stick an alias statement in `~/.{z,ba}shrc` than create a script, invoke another instance of interpreter and then run neovim
|
|
|
|
|
|
|
|
- Telescope live_grep on Git root
- Update README.md: windows powershell
|
|
Differences in CMD and Powershell env variables.
|
|
|
|
|
|
|
|
Added information on where to install if you use Powershell in windows. Since CMD and Powershell work differently.
`%userprofile%` only works for the CMD application.
`$env:USERPROFILE` works in Powershell.
|
|
|
|
Change the recommendation to just run nvim normally instead of the headless
mode for the first run. This will show Lazy UI updating the plugins which
would match what the video show and may be easier to understand what is going
on thant the silent headless run.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Update README.md with a GitHub friendly video example
|
|
Hey y'all 👋
I think there may have been a typo?
|
|
|
|
fix(docs): whoops missed another instance of `nvim-data`
|
|
|
|
|
|
Fix for #314 - there's no -data at the end of the nvim dir.
|
|
|
|
Tiny wording changes I requested from https://github.com/nvim-lua/kickstart.nvim/pull/283
|
|
My browser should not be caching yet github seems to fight some changes. I'm also still unable to see why the formatting (line height) differs between the Archive Install section and the Git Clone Install section.
Hopefully this will at least save the correct changes to the Win stuff.
|
|
|
|
Tested on a win10VM for location and such because I remembered %appdata% should be a thing but it's the wrong location and the win MSI creates nvim-data rather than just nvim. Then I noticed my previous changes weren't all saved...so here I go again heh.
|
|
|
|
I fear adding bits like "Your paths may differ, these are just for reference." but the core behind the kickstart is getting "noobs" past big hurdles fast. This however means things need to be super spoon fed or basic things like not understanding relative paths and such might end up right where things started...ambiguous to some user instructions because they don't understand they need to know certain things because this is supposed to help them bypass knowing that for now...and the snake eats its tail. :)
|
|
|
|
|
|
|
|
|
|
|
|
For me, setting this variable in the config function didn't work. Putting it outside the return block did the trick.
|
|
|
|
Closes #175
Closes #177
Closes #173
Closes #169
Closes #161
Closes #144
Closes #138
Fixes #136
Closes #137
Closes #131
Closes #117
Closes #130
Closes #115
Closes #86
Closes #105
Closes #70
Fixes #176
Fixes #174
Fixes #160
Fixes #158
|
|
* feat: add init.lua location fir Windows
* feat: more specific number of lines
|
