Based on:
commit 177ff6148391742ccb7aaa93c05b95cd6fc853e2
Author: orip <oriori1703@gmail.com>
AuthorDate: Sat Apr 26 14:35:04 2025 +0300
Add type hints to plugin options where possible
This could help beginners to get autocompletion, catch mistakes earlier,
and allow them to skip the docs for simple configs.
This is not perfect because a lot of the plugins type all of their keys
as required, even though they have defaults, but this is good enough.
- fix: rename vim.highlight.on_yank to vim.hl.on_yank
- README: mention fd-find in requirements
- don't lazy-load neo-tree so netrw hijacking on startup works
- Replace vim.opt with vim.o
- feat: switch vim-sleuth for guess-indent.nvim
- Change to Mason's new address
- 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()
* 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
Note, the upstream base gitsigns config and optional gitsigns plugin are merged
into the same plugin spec, so the gitsigns keymaps are enabled by default.
