dylan/nvim-dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
337 Commits 1 Branch 0 Tags
e64aa51ef29dfd17bf44711c697f00caff195165
Commit Graph
185 Commits
Author SHA1 Message Date
Jonas ZeltnerandGitHub e64aa51ef2 fix: regression introduced in db78c0b217 (#1367) 2025-02-18 11:15:13 -05:00
Aryan RajoriaandGitHub 7c49ba1cb7 Fix: fix the cmp-nvim-lsp-signature-help link (#1363) 2025-02-18 00:05:15 -05:00
RobGitHubmakeworld
 		282cbb9c82 feat: add basic function signature help (#1358) 
* feat: add basic function signature help

* Update init.lua

Co-authored-by: makeworld <[email protected]>

---------

Co-authored-by: makeworld <[email protected]>
 2025-02-17 19:12:06 -05:00
Joaquín GuerraandGitHub ebca680dea perf: load tokyonight.nvim in the intended way (#1360) 
Fixes #1357
 2025-02-17 19:10:48 -05:00
GeloCraftGitHubgelocraft
 		76e06fec5c feat(diagnostic): add diagnostic config (#1335) 
Co-authored-by: gelocraft <[email protected]>
 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
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
Diorman ColmenaresandGitHub 5bdde24dfb Use luals 3rd library for luv (#1303) 2025-01-15 14:38:26 -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
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
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
gloomy-lemon-debatableGitHubname <email>
 		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
samGitHubsam
 		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 <[email protected]>
 2024-10-30 11:49:16 -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
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
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
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
Vladislav GrechannikGitHubMatt Mirusmrr11kSeb Tomasini
 		7513ec8a7d Neovim 0.10 updates (#936) 
* Neovim 0.10 updates

Provide the buffer for which to enable inlay hints

Co-authored-by: Matt Mirus <[email protected]>

* 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 <[email protected]>
Co-authored-by: mrr11k <[email protected]>
Co-authored-by: Seb Tomasini <[email protected]>
 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
TJ DeVries 2df5137e59 fix: add required parsers from nvim-treesitter 2024-07-17 21:37:31 -04:00
Folke LemaitreandGitHub 3e55ff1a83 fix(lazy): added error handling for bootstrap (#1001) 2024-07-16 12:06:47 -04:00
Vladislav GrechannikandGitHub f5c919558b which-key v3 update (#1022) 
* which-key v3 update

* remove unneeded brackets from which-key registration
 2024-07-16 12:05:40 -04:00
Richard MacklinandGitHub f86f18f27a Add diff to treesitter's ensure_installed languages (#908) 2024-05-05 21:01:39 -04:00
Damjan 9000andGitHub 6f6f38a6b5 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.
 2024-05-02 16:53:07 -04:00
Francis BelangerandGitHub 942b26184c fix: highlight group clear on each attach (#874) 2024-04-22 15:53:45 -04:00
Francis BelangerGitHubFrancis Belanger
 		81f270a704 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 <[email protected]>
 2024-04-22 11:43:10 -04:00
Vladislav GrechannikandGitHub f92fb11d68 Fix deprecation notice of inlay hints (#873) 2024-04-22 07:27:13 -04:00
Damjan 9000andGitHub 2e68a2c253 Add a commented out example of the classic complete keymaps. Fixes #866 (#868) 2024-04-20 13:14:49 -04:00
GameFuzzyandGitHub b07176aef6 fix: restore Mason config timing for DAP startup (again) (#865) 2024-04-19 13:50:42 -04:00
Damjan 9000andGitHub f5c9fe8e15 Add gitsigns recommended keymaps as an optional plugin (#858) 2024-04-17 21:00:39 -04:00
Damjan 9000andGitHub 5e258d276f 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
 2024-04-17 15:25:54 -04:00
Vladislav GrechannikandGitHub 5540527fab Enable inlay hints for the supporting servers (#843) 2024-04-17 14:04:55 -04:00