This repository has been archived by the owner on Jan 3, 2024. It is now read-only.
feat: Make inlay_hints priority configurable #361
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
MunifTanjim
pushed a commit
to MunifTanjim/rust-tools.nvim
that referenced
this pull request
May 20, 2023
|
I've pulled this in https://github.com/MunifTanjim/rust-tools.nvim/tree/patched |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I'm using
gitsignswith thecurrent_line_blameconfiguration enabled. This basically shows the last change on the current line as virtual text.For
rustI would like to see theinlay_hintsfirst and the blame information second. By defaultgitsignsuses a priority of100(which I think is also the default in general, but couldn't find it in the docs).This PR would make it possible to set the priority of the
inlay_hintsin the configuration ofrust-tools.nvimand therefore create your own custom ordering (even if you have 15 more plugins for virtual text).To my knowledge it doesn't change the default behaviour (which would put gitsigns blame in front)