Commit Graph

223 Commits

Author SHA1 Message Date
jordanyono e01be2e14a Merge branch 'master' of https://github.com/jyono/kickstart.nvim 2025-10-21 11:22:13 -04:00
jordanyono 1c6512d227 no write 2025-10-21 11:22:08 -04:00
Jordan Yono c577052c67 nerd font 2025-10-20 06:24:52 -04:00
jordanyono b44766ba67 yayaya 2025-10-16 22:35:33 -04:00
jordanyono d2edadcbe1 fix 2025-10-13 14:04:51 -04:00
jordanyono 70d8b82df2 more treesitting 2025-10-13 13:54:00 -04:00
jordanyono a1f1968cb3 ts configgy 2025-10-09 14:33:19 -04:00
jordanyono c81ec8776f trhing 2025-10-08 11:11:29 -04:00
jordanyono 5f7f4fae24 add gopls 2025-10-08 11:00:42 -04:00
jordanyono 427af219d8 add 2025-10-08 10:46:59 -04:00
jordanyono 3fb64a9be1 paste no yank 2025-09-19 15:18:43 -04:00
jordanyono cd9f5a7eb1 blame 2025-09-12 06:46:29 -04:00
jordanyono 37a2b56005 blame 2025-09-12 06:45:15 -04:00
jordanyono 903b0c8b22 blame 2025-09-12 06:43:28 -04:00
jordanyono 2f469766cc update 2025-09-02 16:36:56 -04:00
jordanyono ce74176b29 lock and load 2025-08-18 17:14:00 -04:00
jordanyono 2bddc423c7 neotree 2025-08-12 19:45:04 -04:00
jordanyono 47be0540ec thing 2025-08-04 22:49:05 -04:00
jordanyono 81f2e7c7fd gitsigns 2025-08-04 11:45:50 -04:00
jordanyono e224bba226 thangs 2025-08-04 11:35:21 -04:00
jordanyono e214fab668 add nvim-tree 2025-08-01 15:08:03 -04:00
jordanyono 868feb4383 gd 2025-07-24 13:08:32 -04:00
jordanyono 9bae26dd5a init lua 2025-07-24 12:52:44 -04:00
jordanyono e1aee4bb95 things 2025-07-24 12:33:19 -04:00
jordanyono a26816c422 sync 2025-07-17 10:26:38 -04:00
Omri Sarig 6ba2408cdf
fix: rename vim.highlight.on_yank to vim.hl.on_yank (#1482)
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>
2025-05-10 20:29:04 -04:00
Ori Perry c92ea7ca97
Replace vim.opt with vim.o (#1495)
* 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
2025-05-10 20:16:03 -04:00
guru245 2b2f0f8364
feat: switch vim-sleuth for guess-indent.nvim (#1512) 2025-05-10 20:11:50 -04:00
guru245 76cb865e4f
Change to Mason's new address (#1516) 2025-05-09 19:41:44 -04:00
Liam Dyer d350db2449
feat: switch nvim-cmp for blink.cmp (#1426) 2025-04-09 17:25:57 -04:00
Dmytro Onypko 9929044f24
Remove Telescope `0.1` branch lock (#1448) 2025-04-09 11:05:40 -04:00
Theo P. 1a5787bc57
Change LSP Keybindings to Match the Default `gr` Bindings Introduced in 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
2025-04-09 11:01:57 -04:00
dasvh 8a5a52f647
fix: minor misspellings (#1450)
* fix: minor misspellings

* revert change for `-Bbuild`
2025-04-09 10:39:17 -04:00
Sander e947649cb0
feat(keymap): move windows without `<C-w>` (#1368) 2025-03-24 15:34:57 -04:00
RulentWave 5e2d7e184b
changed Conform's format_on_save lambda so that buffers that match 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) 2025-03-24 15:33:53 -04:00
Crypto-Spartan 38f4744e25
feat: add `vim.opt.confirm = true` (#1384) 2025-03-12 17:24:44 -04:00
Chris Patti 34e7d29aa7
Propsed fix for init.lua warnings as per https://github.com/nvim-lua/kickstart.nvim/issues/1305#issuecomment-2657770325 (#1354) 2025-02-19 09:40:16 -05:00
Ari Pollak ea60b2b01f
Remove duplicate cmp-path (#1369) 2025-02-19 09:38:58 -05:00
Jonas Zeltner e64aa51ef2
fix: regression introduced in db78c0b217 (#1367) 2025-02-18 11:15:13 -05:00
Aryan Rajoria 7c49ba1cb7
Fix: fix the cmp-nvim-lsp-signature-help link (#1363) 2025-02-18 00:05:15 -05:00
Rob 282cbb9c82
feat: add basic function signature help (#1358)
* 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>
2025-02-17 19:12:06 -05:00
Joaquín Guerra ebca680dea
perf: load tokyonight.nvim in the intended way (#1360)
Fixes #1357
2025-02-17 19:10:48 -05:00
GeloCraft 76e06fec5c
feat(diagnostic): add diagnostic config (#1335)
Co-authored-by: gelocraft <gelocraft@users.noreply.github.com>
2025-02-17 13:01:07 -05:00
Jonas Zeltner db78c0b217
fix: arguments for the `vim.lsp.Client.supports_method` method (#1356) 2025-02-16 22:42:19 -05:00
bleacheda 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 Colmenares 5bdde24dfb
Use luals 3rd library for luv (#1303) 2025-01-15 14:38:26 -05:00
Nhan Luu f6abf682ff
chore: remove redundant comment (#1307) 2025-01-15 14:37:03 -05:00
Tomas Gareau 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 Jensen 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.

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.
2024-12-29 12:04:10 -05:00
ben fleis 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