Commit Graph

215 Commits

Author SHA1 Message Date
Tawfeeq f9c03f815f Added spelling plugin? 2025-06-27 10:39:34 +02:00
Tawfeeq a4b3ca3a82 update obsidian 2025-04-25 14:49:12 +02:00
Tawfeeq e9d73e2249 obsidian and update to telescope for hidden files 2025-04-17 11:07:06 +02:00
Tawfeeq ffdb9eb0e5 updated bufferline 2025-04-06 14:09:10 +02:00
Tawfeeq 9f9d663f0b themes and lualine 2025-04-05 04:01:45 +02:00
Tawfeeq fbbbd26e08 more stuff 2025-04-01 10:57:06 +02:00
Tawfeeq b9199efb56 many theme changes 2025-03-27 15:01:15 +01:00
Tawfeeq Meeri 2730fd29b8
Merge branch 'master' into develop 2025-03-27 14:59:04 +01:00
Tawfeeq Meeri 510c5a56f5
Merge branch 'nvim-lua:master' into master 2025-03-27 14:54:45 +01:00
Tawfeeq f90f5456fa updated e-ink config 2025-03-27 01:30:45 +01:00
Tawfeeq a21357c5ec Added completiong to dadbod 2025-03-26 09:53:33 +01: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
Tawfeeq 019526c694 Added treesitter-textobjects 2025-03-11 12:17:10 +01:00
Tawfeeq 9a4ca7c839 added more to the ensure installed of treesitter 2025-03-11 11:10:44 +01:00
Tawfeeq 198370ae5b uncommented gitsigns 2025-03-10 19:56:09 +01:00
Tawfeeq ad4804d39b changed cursor to block 2025-02-26 14:46:05 +01:00
Tawfeeq Meeri 314474996c
Merge branch 'master' into develop 2025-02-26 14:43:48 +01: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
Tawfeeq e88427bcf6 fixed lualine config and neotree startup 2025-02-10 16:42:52 +01:00
Tawfeeq 770feee470 updated transparency 2025-02-08 00:16:40 +01:00
Tawfeeq ed9ef123c1 deleted some themes 2025-02-05 23:58:33 +01:00
Tawfeeq 8d05a545d1 added debugger vscode js 2025-01-19 11:54:28 +01: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
Tawfeeq 4b43e2f49e added floating terminal and snacks 2024-12-19 14:07:15 +01: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
Artem Dragunov a2df3ea9eb
Use consistent syntax style for { ... } "pseudocode" (#1247)
```
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)
2024-12-12 10:51:58 -05:00
ben fleis 7bc9d19a4d
Tweak outdated comment about lazy's `config` key usage. (#1250)
Remove outdated comment describing use of `config` key, replacing with
corrected `opt` key note.

Fixes #1249
2024-12-12 10:50:55 -05:00
Miha 8d1ef972bc
fix: which-key comment typo (#1227) 2024-11-20 08:41:50 -05:00
gloomy-lemon-debatable e5dc5f6d1c
feat: Change to prepare for upcoming deprecation of configuring diagnostic-signs using sign_define() (#1232) 2024-11-20 08:37:22 -05:00
Will Winder 2ba39c6973
Remove two because there are more than two. (#1213) 2024-10-30 14:58:52 -04:00
gloomy-lemon-debatable d09d9bc6dc
Change diagnostic symbols if vim.g.have_nerd_font is true (#1195)
* 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>
2024-10-30 11:50:27 -04:00
sam fb7f6a1c13
samarth-nagar fix: lazy help tag on line 931 (#1167)
* 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>
2024-10-30 11:49:16 -04:00
Tawfeeq 1f8a7a4eda c sharp 2024-09-20 23:47:43 +02:00
Nicolás Baquero 7201dc4801
feat: update references of tsserver to ts_ls (#1131) 2024-09-10 16:27:24 -04:00
tawfeeq 7a26e6c951 new themes 2024-08-28 18:55:57 +02:00
Damjan 9000 a22976111e
Fix the which-key spec issue caused by recent cleanup (#1113)
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.
2024-08-26 16:43:59 -04:00
Ihsan Tonuzi 24d368f9ff
cleanup: refactor which-key configuration for cleaner setup (#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 #1068.
2024-08-26 12:17:22 -04:00