| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Merged commits from upstream:
Update comment about the toggle inlay hints keymap
lint: fix lsp warning in `vim.lsp.inlay_hint.is_enabled`
Update lazydev config to fix "Undefined field `fs_stat`" LSP error
Neovim 0.10 updates
Fix comment about mini.ai example
Make conform.nvim be lazy-loadable again
Update README.md | %userprofile%\appdata\local -> %localappdata%
Make debug lazy loadable
Remove redundant require
Fix neo-tree keymap description
fix: add required parsers from nvim-treesitter
|
|
- Replace `%userprofile%\AppData\Local\nvim\` and `$env:USERPROFILE\AppData\Local\nvim` to `%localappdata%\nvim` and `$env:LOCALAPPDATA\nvim respectfully`
|
|
|
|
Fixes: #884
Neovim requires an external tool for proper system clipboard integration.
Some systems install this already by default:
- on Fedora xsel is already installed by default
- on Windows using the choko install the win32yank is alredy installed
This is not installed by default on ubuntu or debian so adding that
to the dependencies list and to the install instructions snippets.
|
|
|
|
Line 102. Placed 'also' before the 'includes'.
"That includes also examples of adding popularly requested plugins." ---> "That also includes examples of adding popularly requested plugins."
|
|
- Add a commented out example of the classic complete keymaps.
- Minor improvements of debian install instructions.
|
|
|
|
|
|
Attempted fix for #859, provide reasonable Debian install instructions -- comment on GitHub issue with refinement.
|
|
|
|
* 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
|
|
|
|
|
|
section
|
|
|
|
- Add `'luadoc'`, to the `ensure_installed` of `nvim-treesitter/nvim-treesitter`
- Add instructions to quit :lazy
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change statusline location to LINE:COLUMN
chore: remove trailing spaces from readme
chore: link new installation youtube video
|
|
|
|
|
|
fix: add note in readme for custom plugins
README.md: updated windows install instructions (#674)
feat: use VimEnter event instead of VeryLazy (#673)
|
|
|
|
|
|
|
|
|
|
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
-------------------------------------------------------------------------------
```
|
|
|
|
|
|
"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.
|
