* Update README (#832)
* Arch, btw (#852)
* Arch, btw
* Add unzip
* Add unzip for Fedora and --needed arg for Arch
* Comment about nerd font selection. Fixes#853 (#854)
* Fix: #847 - add prefer_git to treesitter config (#856)
* Enable inlay hints for the supporting servers (#843)
* Move plugin examples from README to optional plugin files (#831)
* Move autopairs example from README to an optional plugin
* Move neo-tree example from README to an optional plugin
* Add gitsigns recommended keymaps as an optional plugin (#858)
* fix: restore Mason config timing for DAP startup (again) (#865)
* Update README.md (#860)
Attempted fix for #859, provide reasonable Debian install instructions -- comment on GitHub issue with refinement.
* Minor improvements of debian install instructions. Fixes#859 (#869)
* Add a commented out example of the classic complete keymaps. Fixes#866 (#868)
* Fix deprecation notice of inlay hints (#873)
* Fix highlight errors when lsp crash or stop (#864)
* Fix highlight errors when lsp crash or stop
It adds a check wether the client is still available before
highlighting.
If the client is not there anymore it returns `true` to unregister the
autocommand
This fix the
`method textDocument/documentHighlight is not supported by any of the servers registered for the current buffer`
errors when doing a LspRestart or the server crashes
* Delete the highlight autocommands in the LspDetatch event
* Only delete autocmds for the current buffer with the group name
* Simplify clearing the autocommands
---------
Co-authored-by: Francis Belanger <francis.belanger@ubisoft.com>
* fix: highlight group clear on each attach (#874)
* Update README.md (#875)
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."
* README: add clipboard tool dependency (#886)
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.
* Move LspDetach handler near kickstart-lsp-highlight group (#900)
Moved to make sure the kickstart-lsp-highlight group exists when
the LspDetach handler is invoked. The LspDetach handler is used
to clean up any lsp highlights that were enabled by CursorHold
if the LSP is stopped or crashed.
* Add diff to treesitter's ensure_installed languages (#908)
* fix: debug.lua (#918)
* Automatically set detached state as needed. (#925)
* Automatically set detached state as needed.
* Use vim.fn.has instead.
* Fix int vs bool.
* which-key v3 update (#1022)
* which-key v3 update
* remove unneeded brackets from which-key registration
* fix(lazy): added error handling for bootstrap (#1001)
* fix: add required parsers from nvim-treesitter
* Fix neo-tree keymap description (#932)
The lazy.nvim keys parameter does not need the `desc` to
be inside a table in the way that vim.keymap.set() does.
With this fix the keymap description will be properly
shown for example in telescope keymap search
* Remove redundant require (#959)
* Make debug lazy loadable (#978)
* Update README.md | %userprofile%\appdata\local -> %localappdata% (#963)
- Replace `%userprofile%\AppData\Local\nvim\` and `$env:USERPROFILE\AppData\Local\nvim` to `%localappdata%\nvim` and `$env:LOCALAPPDATA\nvim respectfully`
* Make conform.nvim be lazy-loadable again (#977)
The PR that disabled lazy loading (#818) was to fix plugin not being
loaded before write. This sets up lazy to load conform before write.
* Fix comment about mini.ai example (#985)
This example wasn't using `'` so this makes more sense
* Neovim 0.10 updates (#936)
* Neovim 0.10 updates
Provide the buffer for which to enable inlay hints
Co-authored-by: Matt Mirus <matt@mattmirus.com>
* refactor: replace vim.loop with vim.uv
* Upgrade folke/neodev (sunsetting) to folke/lazydev
* Update checkhealth for 0.10 release
---------
Co-authored-by: Matt Mirus <matt@mattmirus.com>
Co-authored-by: mrr11k <me+github@mrr11k.dev>
Co-authored-by: Seb Tomasini <sebt@qgates.com>
* Update lazydev config to fix "Undefined field `fs_stat`" LSP error (#1040)
7513ec8a7d switched from neodev to
lazydev, but in the process it introduced an LSP error in `init.lua`,
which degrades the desired "first timer" experience of kickstart.nvim.
This commit follows the configuration suggested in
6184ebbbc8 (-installation)
which resolves the LSP error.
* lint: fix lsp warning in `vim.lsp.inlay_hint.is_enabled` (#947)
* fix: lsp warning
* review suggestion
Co-authored-by: Tom Kuson <mail@tjkuson.me>
---------
Co-authored-by: Tom Kuson <mail@tjkuson.me>
* Update comment about the toggle inlay hints keymap (#1041)
* Remove redundant hlsearch option (#1058)
* Modify conform comments to prevent deprecation warning when used (#1057)
* refactor: remove lazydev and luvit-meta as lsp dependencies (#1047)
* performance: defer clipboard because xsel and pbcopy can be slow (#1049)
* Remove treesitter prefer_git option (#1061)
- It's not safe and can corrupt other git repos
- nvim-treesiter maintainers consider `prefer_git` as deprecated and no
longer needed.
See nvim-treesitter PR for details: https://github.com/nvim-treesitter/nvim-treesitter/pull/6959
* Add explicit dependency of nvim-lspconfig on cmp-nvim-lsp (#1042)
* Update README.md (#1091)
* Add note in README about lazy-lock.json (#1090)
* Check for loop or uv for lazypath (#1095)
* refactor: update treesitter and which-key config (#1068)
* Include visual mode in LSP code action keymap (#1060) (#1064)
* Enable silent option for default neo-tree plugin keybinding (#1108)
* Fix: updated the windows installation commands (#1101)
* Update README.md
* Update README.md
* Fix: updated the windows installation commands
* fix: remove deprecated opt for conform.nvim (#1070)
- changed lsp_fallback -> lsp_format
- updated format_on_save function to reflect change above
* cleanup: refactor which-key configuration for cleaner setup (#1102)
- Moved `which-key` configuration from inline `config` to `opts` for better organization.
- Updated the key mappings setup to use `spec` for defining existing key chains.
- Removed deprecated or unnecessary comments and code.
This change aligns with updated `which-key` configuration practices, improving readability and maintainability as recommended by @VlaDexa in #1068.
* Fix the which-key spec issue caused by recent cleanup (#1113)
The recent cleanup accidentally broke the leader key specs
because the spec block was in the wrong level of braces.
That resulted in which-key no longer showing the description
of the <leader> key chains such as [S]earch and others.
* feat: update references of tsserver to ts_ls (#1131)
* fix: update lazy uninstall information link (#1148)
* Disable linting autocmd for readonly buffers (#1202)
* Disable linting autocmd for readonly buffers
This should avoid linting in buffers outside of the user's control,
having in mind especially the handy LSP pop-ups that describe your
hovered symbol using markdown.
Co-authored-by: Robin Gruyters <2082795+rgruyters@users.noreply.github.com>
* Justify guarding try_lint in readonly buffers
Co-authored-by: Robin Gruyters <2082795+rgruyters@users.noreply.github.com>
---------
Co-authored-by: Robin Gruyters <2082795+rgruyters@users.noreply.github.com>
* samarth-nagar fix: lazy help tag on line 931 (#1167)
* samarth-nagar fix: lazy help tag on line 931
found in issue #1152
* fixed white space
---------
Co-authored-by: sam <110125971+samarth-nagar@users.noreply.github.com>
* Change diagnostic symbols if vim.g.have_nerd_font is true (#1195)
* feat: Change diagnostic symbols if vim.g.have_nerd_font is true
* feat: Comment out changes regarding diagnostic symbols so that only those who want to change them can do so
---------
Co-authored-by: name <email>
* Set breakpoint icons and their highlight colors (#1194)
* feat: Set breakpoint icons and their highlight colors
* docs: Delete reference URL (written in PR)
feat: "Break" and "Stop" arguments of vim.api.nvim_set_hl are changed because they are too common nouns
feat: Comment out changes regarding diagnostic symbols so that only those who want to change them can do so
---------
Co-authored-by: name <email>
* Remove two because there are more than two. (#1213)
* feat: Change to prepare for upcoming deprecation of configuring diagnostic-signs using sign_define() (#1232)
* Fix nvim-dap not lazy loading (#1216)
* Fix nvim-dap not lazy loading
The keys property had local variables 'dap' and 'dap-ui' that used `require` and prevented all DAP related plugins from lazy-loading.
Fixed this by changing keys to a table and substituting the local variables with a lamba function
* Make debug keybind descriptions more consistent
* fix: which-key comment typo (#1227)
* Tweak outdated comment about lazy's `config` key usage. (#1250)
Remove outdated comment describing use of `config` key, replacing with
corrected `opt` key note.
Fixes#1249
* Use consistent syntax style for { ... } "pseudocode" (#1247)
```
require('gitsigns').setup({ ... })
```
This was the first occurrence
It may be nice to have the same style everywhere
Cosmetic change (just to make docs/comments even more perfect)
* Issue 1249 which key comments (#1263)
* Tweak outdated comment about lazy's `config` key usage.
Remove outdated comment describing use of `config` key, replacing with
corrected `opt` key note.
Fixes#1249
* fix typo opt -> opts
Fixes#1250
* fix(gitsigns): make visual mode descriptions consistent with normal mode (#1266)
* Fix README.md grammar and typos (#1291)
* chore: add pre-issue requirements (#1288)
* chore: add pre-issue requirements
Based on #1285
* docs: add header about documentation
Based on #1285
* Fix which-key delay settings (#1276)
The which-key plugin used to rely on vim.opt.timeoutlen, but it was
updated a few months ago to use its own opt.delay instead.
8ab96b38a2/NEWS.md?plain=1#L10
I set which-key's delay to 0 ms because it makes it feel snappy and
responsive! That way, we give new users a good first impression.
* fix: prevent mason setup from being run twice (#1298)
* fix: prevent mason setup from being run twice
Addresses https://github.com/nvim-lua/kickstart.nvim/issues/1297
Currently, we're calling `require('mason').setup(...)` twice:
* once when setting it as a dependency of `nvim-lspconfig` (since we set
`config = true`)
* once in the `config` function we define for `nvim-lspconfig`
Calling setup twice can cause issues with, e.g., setting the `PATH`
option: you might append Mason's bin dir in one setup call and prepend
it in the other.
We've kept the setup of `mason` in the `nvim-lspconfig` dependencies
table since leaving it to the `config` function caused some
plugin-loading-order related issues in the past. See:
* https://github.com/nvim-lua/kickstart.nvim/pull/210
* https://github.com/nvim-lua/kickstart.nvim/issues/554
* https://github.com/nvim-lua/kickstart.nvim/pull/555
* https://github.com/nvim-lua/kickstart.nvim/pull/865
* docs: tweak comments per review feedback
* chore: remove redundant comment (#1307)
* chore: fix typo in bug report issue template (#1306)
* Use luals 3rd library for luv (#1303)
* chore(docs): Update README.md (#1344)
Neovim has renamed the "linux64" binary to "linux-x86_64".
* docs: clarify using opts = {} vs config = function() ... require('plu… (#1316)
* docs: clarify using opts = {} vs config = function() ... require('plugin').setup({}) .. end
The current documentation mentioning that using "require" is equivalent to using "opts" without detailing the use in the "config = function()" block seems inaccurate.
Lower in the configuration the "config = function()" block is used without clarifying why it needed and what it does.
This clarification may help new users understand the difference between the two, or how and where to place the "require" statement.
* Update init.lua
* remove whitespace
* fix (#1319): gitsigns deprecated functions (#1321)
- This commit change two functions that are marked as deprecated now:
`gitsigns.stage_hunk` and `gitsigns.toggle_deleted`
* Add a blurb about installing missing emoji on Ubuntu
Right next to the nerdfonts blurb as requested.
* fix: arguments for the `vim.lsp.Client.supports_method` method (#1356)
* feat(diagnostic): add diagnostic config (#1335)
Co-authored-by: gelocraft <gelocraft@users.noreply.github.com>
* perf: load tokyonight.nvim in the intended way (#1360)
Fixes#1357
* feat: add basic function signature help (#1358)
* feat: add basic function signature help
* Update init.lua
Co-authored-by: makeworld <25111343+makew0rld@users.noreply.github.com>
---------
Co-authored-by: makeworld <25111343+makew0rld@users.noreply.github.com>
* Fix: fix the cmp-nvim-lsp-signature-help link (#1363)
* fix: regression introduced in db78c0b217 (#1367)
* Remove duplicate cmp-path (#1369)
* Propsed fix for init.lua warnings as per https://github.com/nvim-lua/kickstart.nvim/issues/1305#issuecomment-2657770325 (#1354)
* feat: add `vim.opt.confirm = true` (#1384)
* fix: use correct github abmonition syntax (#1414)
* changed Conform's format_on_save lambda so that buffers that match disable_filetypes return nil. This allows you to enable a formatter for langages in the disable_filetypes table to have a formatter that can be run manually with Leader-f but doesnt enable format_on_save for them (#1395)
* feat(keymap): move windows without `<C-w>` (#1368)
* fix: minor misspellings (#1450)
* fix: minor misspellings
* revert change for `-Bbuild`
* Change LSP Keybindings to Match the Default `gr` Bindings Introduced in Neovim 0.11 (#1427)
* refactor: change LSP keybindings to the default gr bindings introduced in 0.11
* refactor: modify existing LSP functions to follow convention
* Remove Telescope `0.1` branch lock (#1448)
* feat: switch nvim-cmp for blink.cmp (#1426)
---------
Co-authored-by: Viet <51826956+hoangvietdo@users.noreply.github.com>
Co-authored-by: rdvm <git@rvm.dev>
Co-authored-by: Damjan 9000 <damjan.9000@gmail.com>
Co-authored-by: Chris Patti <feoh@feoh.org>
Co-authored-by: Vladislav Grechannik <52157081+VlaDexa@users.noreply.github.com>
Co-authored-by: GameFuzzy <mail@gamefuzzy.dev>
Co-authored-by: Evan Carroll <me@evancarroll.com>
Co-authored-by: Francis Belanger <francis.belanger@gmail.com>
Co-authored-by: Francis Belanger <francis.belanger@ubisoft.com>
Co-authored-by: Adolfo Gante <adolfogante@gmail.com>
Co-authored-by: Richard Macklin <1863540+rmacklin@users.noreply.github.com>
Co-authored-by: Smig <89040888+smiggiddy@users.noreply.github.com>
Co-authored-by: Per Malmberg <PerMalmberg@users.noreply.github.com>
Co-authored-by: Folke Lemaitre <folke.lemaitre@gmail.com>
Co-authored-by: TJ DeVries <devries.timothyj@gmail.com>
Co-authored-by: Tom Kuson <mail@tjkuson.me>
Co-authored-by: Artyom <84637383+MZhuvka@users.noreply.github.com>
Co-authored-by: Matt Mirus <matt@mattmirus.com>
Co-authored-by: mrr11k <me+github@mrr11k.dev>
Co-authored-by: Seb Tomasini <sebt@qgates.com>
Co-authored-by: srdtrk <59252793+srdtrk@users.noreply.github.com>
Co-authored-by: Arvin Verain <arvinverain@proton.me>
Co-authored-by: Brandon Clark <bwclark97@gmail.com>
Co-authored-by: Ihsan Tonuzi <115842560+iton0@users.noreply.github.com>
Co-authored-by: abeldekat <58370433+abeldekat@users.noreply.github.com>
Co-authored-by: jstrot <44594069+jstrot@users.noreply.github.com>
Co-authored-by: theoboldalex <44616505+theoboldalex@users.noreply.github.com>
Co-authored-by: Matt Gallagher <46973220+mattgallagher92@users.noreply.github.com>
Co-authored-by: Michael L. <m@lehenauer.com>
Co-authored-by: Bayram Kazik <48856944+bayramkzk@users.noreply.github.com>
Co-authored-by: Harshit Pant <97608579+pantharshit007@users.noreply.github.com>
Co-authored-by: Nicolás Baquero <88566759+Cheveniko@users.noreply.github.com>
Co-authored-by: Bastien Traverse <neitsab@esrevart.net>
Co-authored-by: Éric NICOLAS <ccjmne@gmail.com>
Co-authored-by: Robin Gruyters <2082795+rgruyters@users.noreply.github.com>
Co-authored-by: sam <110125971+samarth-na@users.noreply.github.com>
Co-authored-by: sam <110125971+samarth-nagar@users.noreply.github.com>
Co-authored-by: gloomy-lemon-debatable <91877885+gloomy-lemon-debatable@users.noreply.github.com>
Co-authored-by: Will Winder <wwinder.unh@gmail.com>
Co-authored-by: Anjishnu Banerjee <107052359+kaezrr@users.noreply.github.com>
Co-authored-by: Miha <79801427+mihasket@users.noreply.github.com>
Co-authored-by: ben fleis <benfleis@users.noreply.github.com>
Co-authored-by: Artem Dragunov <dragunovartem99@gmail.com>
Co-authored-by: Scott Swensen <git@scottswensen.com>
Co-authored-by: George <george@primalskill.com>
Co-authored-by: Ryan Jensen <jensenr30@gmail.com>
Co-authored-by: Tomas Gareau <tggareau@gmail.com>
Co-authored-by: Nhan Luu <62146587+nhld@users.noreply.github.com>
Co-authored-by: Diorman Colmenares <229201+diorman@users.noreply.github.com>
Co-authored-by: Ryan Nevius <rnevius@users.noreply.github.com>
Co-authored-by: bleacheda <60625523+bleacheda@users.noreply.github.com>
Co-authored-by: Erlan Rangel <erlanrangel@gmail.com>
Co-authored-by: Jonas Zeltner <jonas.zeltner@posteo.de>
Co-authored-by: GeloCraft <115651305+gelocraft@users.noreply.github.com>
Co-authored-by: gelocraft <gelocraft@users.noreply.github.com>
Co-authored-by: Joaquín Guerra <joaquinguerratocino@gmail.com>
Co-authored-by: Rob <rcsfletcher@protonmail.com>
Co-authored-by: makeworld <25111343+makew0rld@users.noreply.github.com>
Co-authored-by: Aryan Rajoria <57455619+aryan-rajoria@users.noreply.github.com>
Co-authored-by: Ari Pollak <aripollak@users.noreply.github.com>
Co-authored-by: Crypto-Spartan <29098151+Crypto-Spartan@users.noreply.github.com>
Co-authored-by: Luca Saccarola <96259932+saccarosium@users.noreply.github.com>
Co-authored-by: RulentWave <49258216+RulentWave@users.noreply.github.com>
Co-authored-by: Sander <info@mesander.com>
Co-authored-by: dasvh <dasvh@protonmail.com>
Co-authored-by: Theo P. <63016528+theopn@users.noreply.github.com>
Co-authored-by: Dmytro Onypko <vaporif@gmail.com>
Co-authored-by: Liam Dyer <liamcdyer@gmail.com>
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.
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.
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.
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. :)
moustario
Damjan 9000
Chris Patti
E
stgpepper
Nora Ayesha
Chiller Dragon
TJ DeVries
gitressa
Sudo
matt
n-a11s
Pedro Santayana
Luca Saccarola
Erik
Dennis-Rall
Andres Lowrie
Dheepak Krishnamurthy
Pavel 'PK' Kaminsky
Gaurav Bhatnagar
Sumanth Lingappa
nPHYN1T3