-
-
Notifications
You must be signed in to change notification settings - Fork 956
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inlay hint configurable option #4740
Comments
Separator of inlay hint have removed, not needed any more, see https://github.com/neoclide/coc.nvim/blob/master/history.md#2023-08-31 |
Yeah I saw that it was removed. That's why I created this feature request. But I couldn't find out how to place the inlay-hints at the end of the line like they were before, instead of them mandatorily being inline. Is there a way to do this? I searched through the documentation |
No such support as we don't think it's a good idea compare to inline ext markers. |
I'm sure you have your reasons, but I would still like to request this feature. I'm not used to inline markers at all, and would prefer the old style. |
It's an opensource project and as authors you can do whatever you want, but I don't understand why are you so eager to break established habits of your users. It was the same with the floating status notifications around a year ago. |
Sorry for that, mostly because the code could be too complex to maintain. |
No, thank you for your work on this awesome project! |
Just for keeping track on the other issue:
Ref. #4074 |
#5060 added |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I do not like the inline inlay hints.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Make it a configuration option on whether or not separators are used, or where the inlay hint is located. Similar to how the code-lens option is given to choose.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Disabling them, but I'd prefer not to.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: