Christoph's site
summaryrefslogtreecommitdiffstats
path: root/nvim
Commit message (Collapse)AuthorAgeFilesLines
* feat(keymap): move windows without `<C-w>` (#1368)Sander2025-03-241-0/+6
|
* changed Conform's format_on_save lambda so that buffers that match ↵RulentWave2025-03-241-7/+5
| | | | 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)
* fix: use correct github abmonition syntax (#1414)Luca Saccarola2025-03-201-4/+5
|
* nvim: Remove tokyonight colorscheme and replace it with darculaChristoph Schlosser2025-03-163-3/+11
|
* nvim: Remove outdated comment about leader keyChristoph Schlosser2025-03-161-1/+0
|
* nvim: Remove kickstart introChristoph Schlosser2025-03-161-86/+0
|
* nvim: Enable custom pluginsChristoph Schlosser2025-03-162-155/+76
|
* nvim: Disable arrow keys in normal modeChristoph Schlosser2025-03-161-17/+37
|
* nvim: Use relative numbersChristoph Schlosser2025-03-161-20/+47
|
* nvim: Set config to enable nerdfontsChristoph Schlosser2025-03-162-1/+2
|
* nvim: Add AI pluginsChristoph Schlosser2025-03-161-0/+102
|
* nvim: Change leader from space to semicolonChristoph Schlosser2025-03-161-2/+2
|
* nvim: Remove lazy-lock.json from gitignore as recommendedChristoph Schlosser2025-03-162-1/+27
|
* feat: add `vim.opt.confirm = true` (#1384)Crypto-Spartan2025-03-121-0/+5
|
* Propsed fix for init.lua warnings as per ↵Chris Patti2025-02-191-0/+2
| | | | https://github.com/nvim-lua/kickstart.nvim/issues/1305#issuecomment-2657770325 (#1354)
* Remove duplicate cmp-path (#1369)Ari Pollak2025-02-191-1/+0
|
* fix: regression introduced in df7b409dd2056d720cd2cd939f2dd74e310bf488 (#1367)Jonas Zeltner2025-02-181-2/+15
|
* Fix: fix the cmp-nvim-lsp-signature-help link (#1363)Aryan Rajoria2025-02-181-1/+1
|
* feat: add basic function signature help (#1358)Rob2025-02-171-0/+3
| | | | | | | | | | | | * 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>
* perf: load tokyonight.nvim in the intended way (#1360)Joaquín Guerra2025-02-171-4/+8
| | | | Fixes #1357
* feat(diagnostic): add diagnostic config (#1335)GeloCraft2025-02-171-9/+28
| | | | Co-authored-by: gelocraft <gelocraft@users.noreply.github.com>
* fix: arguments for the `vim.lsp.Client.supports_method` method (#1356)Jonas Zeltner2025-02-161-2/+2
|
* Add a blurb about installing missing emoji on UbuntuChris Patti2025-02-161-0/+1
| | | | Right next to the nerdfonts blurb as requested.
* fix (#1319): gitsigns deprecated functions (#1321)Erlan Rangel2025-02-151-2/+2
| | | | | - 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('plu… (#1316)bleacheda2025-02-141-3/+13
| | | | | | | | | | | | * 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
* chore(docs): Update README.md (#1344)Ryan Nevius2025-02-141-6/+6
| | | | Neovim has renamed the "linux64" binary to "linux-x86_64".
* Use luals 3rd library for luv (#1303)Diorman Colmenares2025-01-151-2/+1
|
* chore: fix typo in bug report issue template (#1306)Nhan Luu2025-01-151-1/+1
|
* chore: remove redundant comment (#1307)Nhan Luu2025-01-151-1/+0
|
* fix: prevent mason setup from being run twice (#1298)Tomas Gareau2025-01-071-6/+11
| | | | | | | | | | | | | | | | | | | | | | | | | * 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
* Fix which-key delay settings (#1276)Ryan Jensen2024-12-291-1/+3
| | | | | | | | | | 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 (#1288)Ihsan Tonuzi2024-12-292-3/+15
| | | | | | | | | | * chore: add pre-issue requirements Based on #1285 * docs: add header about documentation Based on #1285
* Fix README.md grammar and typos (#1291)George2024-12-291-7/+7
|
* fix(gitsigns): make visual mode descriptions consistent with normal mode (#1266)Scott Swensen2024-12-151-2/+2
|
* Issue 1249 which key comments (#1263)ben fleis2024-12-121-1/+1
| | | | | | | | | | | | | * 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
* Use consistent syntax style for { ... } "pseudocode" (#1247)Artem Dragunov2024-12-121-2/+2
| | | | | | | | | | | | ``` 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)
* Tweak outdated comment about lazy's `config` key usage. (#1250)ben fleis2024-12-121-3/+2
| | | | | | | Remove outdated comment describing use of `config` key, replacing with corrected `opt` key note. Fixes #1249
* fix: which-key comment typo (#1227)Miha2024-11-201-1/+1
|
* Fix nvim-dap not lazy loading (#1216)Anjishnu Banerjee2024-11-201-22/+53
| | | | | | | | | * 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: Change to prepare for upcoming deprecation of configuring ↵gloomy-lemon-debatable2024-11-201-3/+4
| | | | diagnostic-signs using sign_define() (#1232)
* Remove two because there are more than two. (#1213)Will Winder2024-10-301-1/+1
|
* Set breakpoint icons and their highlight colors (#1194)gloomy-lemon-debatable2024-10-301-0/+12
| | | | | | | | | | | | * 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>
* Change diagnostic symbols if vim.g.have_nerd_font is true (#1195)gloomy-lemon-debatable2024-10-301-0/+9
| | | | | | | | | | * 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 (#1167)sam2024-10-301-1/+5
| | | | | | | | | | | | * 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 (#1202)Éric NICOLAS2024-10-301-1/+6
| | | | | | | | | | | | | | | | | | * 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>
* fix: update lazy uninstall information link (#1148)Bastien Traverse2024-09-241-1/+1
|
* feat: update references of tsserver to ts_ls (#1131)Nicolás Baquero2024-09-101-3/+3
|
* Fix the which-key spec issue caused by recent cleanup (#1113)Damjan 90002024-08-261-10/+10
| | | | | | | 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.
* cleanup: refactor which-key configuration for cleaner setup (#1102)Ihsan Tonuzi2024-08-261-49/+47
| | | | | | | | - 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.
* fix: remove deprecated opt for conform.nvim (#1070)Ihsan Tonuzi2024-08-251-2/+8
| | | | | - changed lsp_fallback -> lsp_format - updated format_on_save function to reflect change above
Privacy Policy