Adds 'gr' to which-keys documentation, so users can see that LSP actions are grouped after 'gr' key binds.
Co-authored-by: thiago-negri <evohunz@gmail.com>
This could help beginners to get autocompletion, catch mistakes earlier,
and allow them to skip the docs for simple configs.
This is not perfect because a lot of the plugins type all of their keys
as required, even though they have defaults, but this is good enough.
* move telescope related lsp functions inside the telscope plugin declaration block
* explicitly enable telescope plugin, add some comments explainging why
* update comments with suggestions from @oriori1703
Co-authored-by: Ori Perry <48057913+oriori1703@users.noreply.github.com>
* fix formatting in accordance to stylua so that pipeline passes
---------
Co-authored-by: Philipp Szechenyi <philipp.szechenyi@cgm.com>
Co-authored-by: Philipp Szechenyi <45265588+szechp@users.noreply.github.com>
Co-authored-by: Ori Perry <48057913+oriori1703@users.noreply.github.com>
Co-authored-by: philipp <philipp@philipps-MacBook-Pro.local>
The functions of vim.highlight were renamed to vim.hl on commit
18b43c331d8a0ed87d7cbefe2a18543b8e4ad360 of neovim, which was applied
with the release of nvim version 0.11.
Now, the use of vim.highlight is deprecated, and instead, one should
use vim.hl functions.
In practice, vim.highlight is still working, however, asking for help
for vim.highlight.on_yank fails (E149), while asking for help for
vim.hl.on_yank works as expected. So, by updating the used function, a
new user will have easier time looking getting the relevant help.
Co-authored-by: Omri Sarig <omri.sarig@prevas.dk>
* Replace vim.opt with vim.o
Because it offers a nicer interface and info on hover.
For now leave vim.opt when using the table interface (until vim.o
with tables is implemented)
* Add type hint for vim.opt.rtp
* Add a comment about using vim.opt instead of vim.o
* 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
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.
```
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)
* 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>
* 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>
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.
- 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.
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.
* 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>
Ori Perry
Nathan Zeng
Ori Perry
Nick Burt
TJ DeVries
Francesc Elies
Derrek
rheia475
Evgeni Chasnovski
Yassine Zouggari
Advin Suryavanshi
Omri Sarig
guru245
Liam Dyer
Dmytro Onypko
Theo P.
dasvh
Sander
RulentWave
Crypto-Spartan
Chris Patti
Ari Pollak
Jonas Zeltner
Aryan Rajoria
Rob
Joaquín Guerra
GeloCraft
bleacheda
Diorman Colmenares
Nhan Luu
Tomas Gareau
Ryan Jensen
ben fleis
Artem Dragunov
Miha
gloomy-lemon-debatable
Will Winder
sam
Nicolás Baquero
Damjan 9000
Ihsan Tonuzi
Bayram Kazik
Michael L.
jstrot
abeldekat
Brandon Clark
Arvin Verain
Richard Macklin
Vladislav Grechannik