Chris Patti
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
Chris Patti
77f71c627f
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
Ari Pollak
ea60b2b01f
Remove duplicate cmp-path ( #1369 )
2025-02-19 09:38:58 -05:00
Ari Pollak
321b2559dc
Remove duplicate cmp-path ( #1369 )
2025-02-19 09:38:58 -05:00
Jonas Zeltner
e64aa51ef2
fix: regression introduced in db78c0b217 ( #1367 )
2025-02-18 11:15:13 -05:00
Jonas Zeltner
076673e5f9
fix: regression introduced in a0b9aaf8b5 ( #1367 )
2025-02-18 11:15:13 -05:00
Aryan Rajoria
7c49ba1cb7
Fix: fix the cmp-nvim-lsp-signature-help link ( #1363 )
2025-02-18 00:05:15 -05:00
Aryan Rajoria
184e95956c
Fix: fix the cmp-nvim-lsp-signature-help link ( #1363 )
2025-02-18 00:05:15 -05:00
Rob
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
Rob
47b17e6dff
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
Joaquín Guerra
ebca680dea
perf: load tokyonight.nvim in the intended way ( #1360 )
...
Fixes #1357
2025-02-17 19:10:48 -05:00
Joaquín Guerra
e27a7418f0
perf: load tokyonight.nvim in the intended way ( #1360 )
...
Fixes #1357
2025-02-17 19:10:48 -05:00
GeloCraft
76e06fec5c
feat(diagnostic): add diagnostic config ( #1335 )
...
Co-authored-by: gelocraft <gelocraft@users.noreply.github.com>
2025-02-17 13:01:07 -05:00
GeloCraft
efcc1e25a5
feat(diagnostic): add diagnostic config ( #1335 )
...
Co-authored-by: gelocraft <gelocraft@users.noreply.github.com>
2025-02-17 13:01:07 -05:00
Jonas Zeltner
db78c0b217
fix: arguments for the vim.lsp.Client.supports_method method ( #1356 )
2025-02-16 22:42:19 -05:00
Jonas Zeltner
a0b9aaf8b5
fix: arguments for the vim.lsp.Client.supports_method method ( #1356 )
2025-02-16 22:42:19 -05:00
Chris Patti
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
Chris Patti
187d3e4519
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
Erlan Rangel
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
Erlan Rangel
ae5d7b6c89
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
bleacheda
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
bleacheda
c057743836
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
Ryan Nevius
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
Ryan Nevius
52f2f309ab
chore(docs): Update README.md ( #1344 )
...
Neovim has renamed the "linux64" binary to "linux-x86_64".
2025-02-14 22:23:31 -05:00
Diorman Colmenares
5bdde24dfb
Use luals 3rd library for luv ( #1303 )
2025-01-15 14:38:26 -05:00
Diorman Colmenares
66ad6d96b8
Use luals 3rd library for luv ( #1303 )
2025-01-15 14:38:26 -05:00
Nhan Luu
ff89769e45
chore: fix typo in bug report issue template ( #1306 )
2025-01-15 14:37:36 -05:00
Nhan Luu
07a5e52ef1
chore: fix typo in bug report issue template ( #1306 )
2025-01-15 14:37:36 -05:00
Nhan Luu
f6abf682ff
chore: remove redundant comment ( #1307 )
2025-01-15 14:37:03 -05:00
Nhan Luu
5c643521f6
chore: remove redundant comment ( #1307 )
2025-01-15 14:37:03 -05:00
Tomas Gareau
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
Tomas Gareau
3700a70d8a
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
Ryan Jensen
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 (L10)
2024-12-29 12:04:10 -05:00
Ryan Jensen
fbe95053c2
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 (L10)
2024-12-29 12:04:10 -05:00
Ihsan Tonuzi
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
Ihsan Tonuzi
d0a75ce25e
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
George
e84e187f3c
Fix README.md grammar and typos ( #1291 )
2024-12-29 11:39:47 -05:00
George
f4486eec72
Fix README.md grammar and typos ( #1291 )
2024-12-29 11:39:47 -05:00
Scott Swensen
de44f49101
fix(gitsigns): make visual mode descriptions consistent with normal mode ( #1266 )
2024-12-15 00:42:39 -05:00
Scott Swensen
b9ccc8414f
fix(gitsigns): make visual mode descriptions consistent with normal mode ( #1266 )
2024-12-15 00:42:39 -05:00
ben fleis
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
ben fleis
1d2247a9d7
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
Artem Dragunov
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
Artem Dragunov
c6b54364ee
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
ben fleis
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
ben fleis
0ef62ad9de
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
Miha
8d1ef972bc
fix: which-key comment typo ( #1227 )
2024-11-20 08:41:50 -05:00
Miha
2b721711b1
fix: which-key comment typo ( #1227 )
2024-11-20 08:41:50 -05:00
Anjishnu Banerjee
9dfb1b230f
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
2024-11-20 08:40:51 -05:00
Anjishnu Banerjee
0d10cd7fa8
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
2024-11-20 08:40:51 -05:00
