| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The functions of vim.highlight were renamed to vim.hl on commit
18b43c331d8a0ed87d7cbefe2a18543b8e4ad360 of neovim, which was applied
with the release of nvim version 0.11.
Now, the use of vim.highlight is deprecated, and instead, one should
use vim.hl functions.
In practice, vim.highlight is still working, however, asking for help
for vim.highlight.on_yank fails (E149), while asking for help for
vim.hl.on_yank works as expected. So, by updating the used function, a
new user will have easier time looking getting the relevant help.
Co-authored-by: Omri Sarig <omri.sarig@prevas.dk>
|
| |
|
|
| |
Fixes #1476
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Replace vim.opt with vim.o
Because it offers a nicer interface and info on hover.
For now leave vim.opt when using the table interface (until vim.o
with tables is implemented)
* Add type hint for vim.opt.rtp
* Add a comment about using vim.opt instead of vim.o
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Neovim 0.11 (#1427)
* refactor: change LSP keybindings to the default gr bindings introduced in 0.11
* refactor: modify existing LSP functions to follow convention
|
| |
|
|
|
|
| |
* fix: minor misspellings
* revert change for `-Bbuild`
|
| | |
|
| |
|
|
| |
disable_filetypes return nil. This allows you to enable a formatter for langages in the disable_filetypes table to have a formatter that can be run manually with Leader-f but doesnt enable format_on_save for them (#1395)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
https://github.com/nvim-lua/kickstart.nvim/issues/1305#issuecomment-2657770325 (#1354)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* 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>
|
| |
|
|
| |
Fixes #1357
|
| |
|
|
| |
Co-authored-by: gelocraft <gelocraft@users.noreply.github.com>
|
| | |
|
| |
|
|
| |
Right next to the nerdfonts blurb as requested.
|
| |
|
|
|
| |
- This commit change two functions that are marked as deprecated now:
`gitsigns.stage_hunk` and `gitsigns.toggle_deleted`
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
|
| |
Neovim has renamed the "linux64" binary to "linux-x86_64".
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
* chore: add pre-issue requirements
Based on #1285
* docs: add header about documentation
Based on #1285
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|