| Age | Commit message (Collapse) | Author |
|---|
|
* Move autopairs example from README to an optional plugin
* Move neo-tree example from README to an optional plugin
|
|
* Arch, btw
* Add unzip
* Add unzip for Fedora and --needed arg for Arch
|
|
|
|
|
|
|
|
|
|
The recommended step of forking the repo coming sequentially after the step instructing users to clone the current repo doesn't make sense.
This commit orders the install instructions in a manner that's more logical.
|
|
|
|
Added file text to code block for consistency since the other plugin had file also inside code block.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We've removed over 1/3 of the code that was in kickstart previously,
and more than doubled the amount of comments explaining every line
of code (to the best of my ability).
kickstart now properly uses many of the lazy.nvim config and loading
idioms, which should be really helpful for people moving both to
modular configs, as well as extending the kickstart config in one file.
Additional features:
- Beautiful ascii art
- Added some documentation that explains what is an LSP, what is telescope, etc
- There is now a `:checkhealth` for kickstart, which checks some basic information
and adds useful information for maintainers (for people cloning the repo).
- Improved LSP configuration and tool installation, for easier first time startup
- Changed init.lua ordering, so that it moves from simple options to complicated config
```
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Lua 1 108 404 298
-------------------------------------------------------------------------------
```
|
|
|
|
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.
|
|
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
|
|
|
|
|
|
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. :)
|
|
|
