update #1
Merged
update #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
* Automatically set detached state as needed. * Use vim.fn.has instead. * Fix int vs bool.
* which-key v3 update * remove unneeded brackets from which-key registration
The lazy.nvim keys parameter does not need the `desc` to be inside a table in the way that vim.keymap.set() does. With this fix the keymap description will be properly shown for example in telescope keymap search
…m-lua#963) - Replace `%userprofile%\AppData\Local\nvim\` and `$env:USERPROFILE\AppData\Local\nvim` to `%localappdata%\nvim` and `$env:LOCALAPPDATA\nvim respectfully`
The PR that disabled lazy loading (nvim-lua#818) was to fix plugin not being loaded before write. This sets up lazy to load conform before write.
This example wasn't using `'` so this makes more sense
* 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]>
…vim-lua#1040) 7513ec8 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.
* fix: lsp warning * review suggestion Co-authored-by: Tom Kuson <[email protected]> --------- Co-authored-by: Tom Kuson <[email protected]>
Merged commits from upstream: Update comment about the toggle inlay hints keymap lint: fix lsp warning in `vim.lsp.inlay_hint.is_enabled` Update lazydev config to fix "Undefined field `fs_stat`" LSP error Neovim 0.10 updates Fix comment about mini.ai example Make conform.nvim be lazy-loadable again Update README.md | %userprofile%\appdata\local -> %localappdata% Make debug lazy loadable Remove redundant require Fix neo-tree keymap description fix: add required parsers from nvim-treesitter
Modify conform comments to prevent deprecation warning when used Remove redundant hlsearch option
performance: defer clipboard because xsel and pbcopy can be slow refactor: remove lazydev and luvit-meta as lsp dependencies
* Ihsan Tonuzi refactor: update treesitter and which-key config * Michael L. Check for loop or uv for lazypath * Matt Gallagher Add note in README about lazy-lock.json * theoboldalex Update README.md
* Update README.md * Update README.md * Fix: updated the windows installation commands
- changed lsp_fallback -> lsp_format - updated format_on_save function to reflect change above
fix: remove deprecated opt for conform.nvim Fix: updated the windows installation commands Enable silent option for default neo-tree plugin keybinding
…#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 nvim-lua#1068.
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.
* 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 <[email protected]> * Justify guarding try_lint in readonly buffers Co-authored-by: Robin Gruyters <[email protected]> --------- Co-authored-by: Robin Gruyters <[email protected]>
* samarth-nagar fix: lazy help tag on line 931 found in issue nvim-lua#1152 * fixed white space --------- Co-authored-by: sam <[email protected]>
* 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>
* Remove two because there are more than two. * Set breakpoint icons and their highlight colors * Change diagnostic symbols if vim.g.have_nerd_font is true * fix: lazy help tag on line 931 * Disable linting autocmd for readonly buffers
…ostic-signs using sign_define() (nvim-lua#1232)
* 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
- fix: which-key comment typo - Fix nvim-dap not lazy loading - feat: Change to prepare for upcoming deprecation of configuring diagnostic-signs using sign_define()
….nvim into update
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
diffto treesitter'sensure_installedlanguages nvim-lua/kickstart.nvim#908)mini.aiexample nvim-lua/kickstart.nvim#985)fs_stat" LSP error (Update lazydev configuration to fix "Undefined fieldfs_stat" LSP error nvim-lua/kickstart.nvim#1040)vim.lsp.inlay_hint.is_enabled(lint: fix lsp warning invim.lsp.inlay_hint.is_enablednvim-lua/kickstart.nvim#947)NOTE
Please verify that the
base repositoryabove has the intended destination!Github by default opens Pull Requests against the parent of a forked repository.
If this is your personal fork and you didn't intend to open a PR for contribution
to the original project then adjust the
base repositoryaccordingly.