82949b8a26
Refactor(lsp): Ensure automatic server enabling
2025-05-17 13:56:36 +02:00
718c90d224
fix: mason server name
2025-05-11 16:16:14 +02:00
f9628e5cad
Merge branch 'master' into master
2025-05-11 15:20:48 +02:00
0018683a23
feat(lsp): Update Mason to v2
2025-05-11 15:18:53 +02:00
6ba2408cdf
fix: rename vim.highlight.on_yank to vim.hl.on_yank ( #1482 )
...
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>
2025-05-10 20:29:04 -04:00
f5a9f9cdc6
README: mention fd-find in requirements ( #1477 )
...
Fixes #1476
2025-05-10 20:23:54 -04:00
fb73617653
don't lazy-load neo-tree so netrw hijacking on startup works ( #1489 )
2025-05-10 20:18:04 -04:00
c92ea7ca97
Replace vim.opt with vim.o ( #1495 )
...
* 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
2025-05-10 20:16:03 -04:00
2b2f0f8364
feat: switch vim-sleuth for guess-indent.nvim ( #1512 )
2025-05-10 20:11:50 -04:00
9e0c7b6341
fix(deps): pin mason plugin versions to v1.*
2025-05-10 17:20:33 +02:00
76cb865e4f
Change to Mason's new address ( #1516 )
2025-05-09 19:41:44 -04:00
81c5210cb5
Fix: correct variables inside comments
...
Co-authored-by: Rory Hendrickson <35480205+roryhen@users.noreply.github.com>
2025-04-30 17:01:57 +02:00
531073d8b2
fix: revert back to original handler logic
2025-04-21 20:02:43 +02:00
dac395dac6
fix: Typo in comment
2025-04-20 13:12:00 +02:00
a590ab6c88
fix(lsp): Remove backwards compatibility and add comments for lsp setup
2025-04-20 12:58:57 +02:00
5502cea3f6
style: format with stylua
2025-04-17 17:22:08 +02:00
4b81900939
fix(lsp): correct variable name in lsp config loop
...
Signed-off-by: Umut Sahin Onder <umutsonder@gmail.com>
2025-04-17 17:17:26 +02:00
f70dcb3373
Typo fix
2025-04-16 19:42:03 +02:00
3f0cd75469
feat: add support for new LSP config API in Neovim 0.11+
2025-04-16 19:34:24 +02:00
d350db2449
feat: switch nvim-cmp for blink.cmp ( #1426 )
2025-04-09 17:25:57 -04:00
9929044f24
Remove Telescope `0.1` branch lock ( #1448 )
2025-04-09 11:05:40 -04:00
1a5787bc57
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
2025-04-09 11:01:57 -04:00
8a5a52f647
fix: minor misspellings ( #1450 )
...
* fix: minor misspellings
* revert change for `-Bbuild`
2025-04-09 10:39:17 -04:00
e947649cb0
feat(keymap): move windows without `<C-w>` ( #1368 )
2025-03-24 15:34:57 -04:00
5e2d7e184b
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 )
2025-03-24 15:33:53 -04:00
2abcb39fae
fix: use correct github abmonition syntax ( #1414 )
2025-03-20 18:16:35 -04:00
38f4744e25
feat: add `vim.opt.confirm = true` ( #1384 )
2025-03-12 17:24:44 -04:00
34e7d29aa7
Propsed fix for init.lua warnings as per https://github.com/nvim-lua/kickstart.nvim/issues/1305#issuecomment-2657770325 ( #1354 )
2025-02-19 09:40:16 -05:00
ea60b2b01f
Remove duplicate cmp-path ( #1369 )
2025-02-19 09:38:58 -05:00
e64aa51ef2
fix: regression introduced in db78c0b217 ( #1367 )
2025-02-18 11:15:13 -05:00
7c49ba1cb7
Fix: fix the cmp-nvim-lsp-signature-help link ( #1363 )
2025-02-18 00:05:15 -05:00
282cbb9c82
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>
2025-02-17 19:12:06 -05:00
ebca680dea
perf: load tokyonight.nvim in the intended way ( #1360 )
...
Fixes #1357
2025-02-17 19:10:48 -05:00
76e06fec5c
feat(diagnostic): add diagnostic config ( #1335 )
...
Co-authored-by: gelocraft <gelocraft@users.noreply.github.com>
2025-02-17 13:01:07 -05:00
db78c0b217
fix: arguments for the `vim.lsp.Client.supports_method` method ( #1356 )
2025-02-16 22:42:19 -05:00
d2c006819a
Add a blurb about installing missing emoji on Ubuntu
...
Right next to the nerdfonts blurb as requested.
2025-02-16 22:37:44 -05:00
94f551b803
fix ( #1319 ): gitsigns deprecated functions ( #1321 )
...
- This commit change two functions that are marked as deprecated now:
`gitsigns.stage_hunk` and `gitsigns.toggle_deleted`
2025-02-15 00:48:37 -05:00
71ad926ab1
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
2025-02-14 22:32:50 -05:00
abdbfce0f8
chore(docs): Update README.md ( #1344 )
...
Neovim has renamed the "linux64" binary to "linux-x86_64".
2025-02-14 22:23:31 -05:00
5bdde24dfb
Use luals 3rd library for luv ( #1303 )
2025-01-15 14:38:26 -05:00
ff89769e45
chore: fix typo in bug report issue template ( #1306 )
2025-01-15 14:37:36 -05:00
f6abf682ff
chore: remove redundant comment ( #1307 )
2025-01-15 14:37:03 -05:00
db4867acb9
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
2025-01-07 10:44:29 -05:00
a8f539562a
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
2024-12-29 12:04:10 -05:00
7ddaab3ffd
chore: add pre-issue requirements ( #1288 )
...
* chore: add pre-issue requirements
Based on #1285
* docs: add header about documentation
Based on #1285
2024-12-29 12:00:16 -05:00
e84e187f3c
Fix README.md grammar and typos ( #1291 )
2024-12-29 11:39:47 -05:00
de44f49101
fix(gitsigns): make visual mode descriptions consistent with normal mode ( #1266 )
2024-12-15 00:42:39 -05:00
bcdb4cd252
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
2024-12-12 16:26:20 -05:00
a2df3ea9eb
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)
2024-12-12 10:51:58 -05:00
7bc9d19a4d
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
2024-12-12 10:50:55 -05:00
Umut Sahin Onder
Umut Önder
Omri Sarig
Damjan 9000
pynappo
Ori Perry
guru245
Liam Dyer
Dmytro Onypko
Theo P.
dasvh
Sander
RulentWave
Luca Saccarola
Crypto-Spartan
Chris Patti
Ari Pollak
Jonas Zeltner
Aryan Rajoria
Rob
Joaquín Guerra
GeloCraft
Erlan Rangel
bleacheda
Ryan Nevius
Diorman Colmenares
Nhan Luu
Tomas Gareau
Ryan Jensen
Ihsan Tonuzi
George
Scott Swensen
ben fleis
Artem Dragunov