This commit introduces new key mappings for enhanced functionality, specifically the F11 key now confirms suggestions in the completion menu while F12 is set to accept Copilot suggestions in insert mode, improving the user experience for code suggestions.
This commit introduces support for formatting HTML by adding 'prettier' to the formatter configuration. This enhancement allows for consistent styling across different file types, improving the coding process.
This commit introduces new key mappings for Telescope to filter document symbols by specific types such as methods, variables, and classes, enhancing the navigation experience by allowing users to efficiently find and access relevant code structures.
This commit introduces configurations for GitHub Copilot and Copilot Chat plugins in the Neovim setup. It includes the setup of keybindings for toggling Copilot and various chat functionalities, enhancing the development experience through AI-assisted programming features.
This change streamlines the lualine configuration by omitting the 'diff' component from the lualine_b section, enhancing clarity and focus on essential information displayed.
This commit adds a configuration for the gruvbox-material colorscheme in the plugins initialization file, enabling automatic application of the colorscheme when loaded.
* 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
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?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.
```
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)
* 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
* 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>
* 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>
* 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>
* 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>