chore: update config #73
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add `Bilal2453/luvit-meta` to resolve LSP warnings related to `vim.uv` types. Updated references from `vim.loop` to `vim.uv` for consistency with `luvit-meta` plugin.
This project is nice but I feel that I'm fighting it too often and it doesn't provide any helpful alternatives to rectify the linter warnings.
fix: update git.change custom color after update Tokyonight v4 changed the name and datatype of this color to `colors.git.change = "#color"` fix: prefer highlight `WinSeparator` over `VertSplit` `WinSeparator` seems to be the new highlight group for coloring split windows and borders. We can also link `WinSeparator` to `VertSplit` to prevent any compatibility errors with plugins that still use `VertSplit`. fix: set telescope selection highlight to `PmenuSel` fix: remove bg highlight for TreesitterContext refactor: remove sidebar list, use default plugin loader refactor: remove user config that matches default values There is basically no change in style! This just remove any options that already matches the plugins default config values. refactor: remove custom git.change color refactor: remove undesired highlight overrides - Remove color override definition for: String - Remove color override definition for: FoldColumn docs: include/update config docs for plugin options - Copy document comments from example config within plugin README - Remove extra space from luadoc description comments - Update luadoc type for v4: `Highlights` -> `tokyonight.Highlights` - Separate custom highlight groups by plugin
The latest Gitsigns update introduces additional signs for staged hunks. However, the current implementation often results in duplicate signs when modifying already staged sections, likely due to Neovim signcolumn prioritization limitations. To mitigate this, the staged signs functionality has been disabled using the `signs_staged_enable` boolean configuration. Custom signs for various actions remain locally defined to ensure consistent visual cues. Additionally, the previously missing `untracked` sign definition has been added to both the regular and staged sign configurations.
Aligned keybindings in `gitsigns.lua` for easier hunk navigation: - Changed `]c` to `]h` for next hunk movement. - Changed `[c` to `[h` for previous hunk movement.
Refine the file ignore patterns for the Telescope fuzzy finder in Neovim to improve search accuracy and performance. Updated patterns include: - Added trailing slashes to directories like `.git/`, `.pytest_cache/`, `.venv/`, `.yarn/`, `__pycache__/`, `_build/`, `build/`, `node_modules/`, `nvim/runtime/doc/`, and `tags/`. - Added new ignore pattern for the `out/` directory. These changes ensure that directory paths are correctly ignored during searches.
Switch the default terminal to use a floating window for more temporary actions, enhancing the user experience. Also, updated keybindings for easier access to different layouts: - `tf`: Floating window - `ts`: Horizontal split - `tt`: Tab - `tv`: Vertical split These adjustments provide more flexibility for managing long-running or reference terminals.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.