Commit Graph
334 Commits
Author SHA1 Message Date
Joaquín GuerraandGitHub 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
Jonas ZeltnerandGitHub db78c0b217 fix: arguments for the vim.lsp.Client.supports_method method (#1356) 2025-02-16 22:42:19 -05:00
Chris PattiandGitHub 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
Erlan RangelandGitHub 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
bleachedaandGitHub 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
Ryan NeviusandGitHub 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
Diorman ColmenaresandGitHub 5bdde24dfb Use luals 3rd library for luv (#1303) 2025-01-15 14:38:26 -05:00
Nhan LuuandGitHub ff89769e45 chore: fix typo in bug report issue template (#1306) 2025-01-15 14:37:36 -05:00
Nhan LuuandGitHub f6abf682ff chore: remove redundant comment (#1307) 2025-01-15 14:37:03 -05:00
Tomas GareauandGitHub 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
Ryan JensenandGitHub 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.

https://github.com/folke/which-key.nvim/blob/8ab96b38a2530eacba5be717f52e04601eb59326/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.
2024-12-29 12:04:10 -05:00
Ihsan TonuziandGitHub 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
GeorgeandGitHub e84e187f3c Fix README.md grammar and typos (#1291) 2024-12-29 11:39:47 -05:00
Scott SwensenandGitHub de44f49101 fix(gitsigns): make visual mode descriptions consistent with normal mode (#1266) 2024-12-15 00:42:39 -05:00
ben fleisandGitHub 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
Artem DragunovandGitHub 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
ben fleisandGitHub 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
MihaandGitHub 8d1ef972bc fix: which-key comment typo (#1227) 2024-11-20 08:41:50 -05:00
Anjishnu BanerjeeandGitHub 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
gloomy-lemon-debatableandGitHub e5dc5f6d1c feat: Change to prepare for upcoming deprecation of configuring diagnostic-signs using sign_define() (#1232) 2024-11-20 08:37:22 -05:00
Will WinderandGitHub 2ba39c6973 Remove two because there are more than two. (#1213) 2024-10-30 14:58:52 -04:00
be678aa341 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>
2024-10-30 13:01:42 -04:00
d09d9bc6dc 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>
2024-10-30 11:50:27 -04:00
fb7f6a1c13 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>
2024-10-30 11:49:16 -04:00
5ed1bc38dc 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>
2024-10-30 11:41:46 -04:00
Bastien TraverseandGitHub 4120893b8a fix: update lazy uninstall information link (#1148) 2024-09-24 11:06:14 -04:00
Nicolás BaqueroandGitHub 7201dc4801 feat: update references of tsserver to ts_ls (#1131) 2024-09-10 16:27:24 -04:00
Damjan 9000andGitHub a22976111e 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.
2024-08-26 16:43:59 -04:00
Ihsan TonuziandGitHub 24d368f9ff 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.
2024-08-26 12:17:22 -04:00
Ihsan TonuziandGitHub c76c323a7c fix: remove deprecated opt for conform.nvim (#1070)
- changed lsp_fallback -> lsp_format
- updated format_on_save function to reflect change above
2024-08-25 23:28:26 -04:00
Harshit PantandGitHub e4a5300bdb Fix: updated the windows installation commands (#1101)
* Update README.md

* Update README.md

* Fix: updated the windows installation commands
2024-08-25 23:27:46 -04:00
Bayram KazikandGitHub f49cc6c935 Enable silent option for default neo-tree plugin keybinding (#1108) 2024-08-25 23:23:17 -04:00
Bayram KazikandGitHub d452633b35 Include visual mode in LSP code action keymap (#1060) (#1064) 2024-08-24 17:31:43 -04:00
Ihsan TonuziandGitHub ac78e7d9e7 refactor: update treesitter and which-key config (#1068) 2024-08-22 21:00:39 -04:00
Michael L.andGitHub ce0c7340ff Check for loop or uv for lazypath (#1095) 2024-08-22 16:56:33 -04:00
Matt GallagherandGitHub 554a054bf9 Add note in README about lazy-lock.json (#1090) 2024-08-22 16:53:57 -04:00
theoboldalexandGitHub c1ae9092cb Update README.md (#1091) 2024-08-22 16:49:25 -04:00
jstrotandGitHub 1860184830 Add explicit dependency of nvim-lspconfig on cmp-nvim-lsp (#1042) 2024-07-29 20:02:37 -04:00
jstrotandGitHub bb9f84ca8f 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
2024-07-29 20:01:19 -04:00
abeldekatandGitHub 84cc12354d performance: defer clipboard because xsel and pbcopy can be slow (#1049) 2024-07-28 17:41:34 -04:00
Ihsan TonuziandGitHub fd66454c4a refactor: remove lazydev and luvit-meta as lsp dependencies (#1047) 2024-07-28 17:39:34 -04:00
Brandon ClarkandGitHub 1cef2325e0 Modify conform comments to prevent deprecation warning when used (#1057) 2024-07-28 12:43:08 -04:00
Arvin VerainandGitHub f00b2866de Remove redundant hlsearch option (#1058) 2024-07-28 12:39:54 -04:00
Richard MacklinandGitHub 56b9114bf2 Update comment about the toggle inlay hints keymap (#1041) 2024-07-22 13:00:35 -04:00
6f3fe35de3 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>
2024-07-21 22:21:21 -04:00
Richard MacklinandGitHub 620732789b 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
https://github.com/folke/lazydev.nvim/tree/6184ebbbc8045d70077659b7d30c705a588dc62f#-installation
which resolves the LSP error.
2024-07-21 22:08:09 -04:00
7513ec8a7d 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>
2024-07-21 20:35:07 -04:00
Richard MacklinandGitHub 07a9f446a3 Fix comment about mini.ai example (#985)
This example wasn't using `'` so this makes more sense
2024-07-21 16:34:51 -04:00
Vladislav GrechannikandGitHub b36d84ddf0 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.
2024-07-21 16:34:17 -04:00