The Wayback Machine - https://web.archive.org/web/20210725112616/https://github.com/prabirshrestha/vim-lsp/issues/1074
Skip to content

/ vim-lsp

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

Jump to bottom

Feature request: plug mapping or command for diagnostics under cursor #1074

Open
paradigm opened this issue Feb 25, 2021 · 5 comments
Open

Feature request: plug mapping or command for diagnostics under cursor #1074

paradigm opened this issue Feb 25, 2021 · 5 comments
Labels
enhancement good first issue

Comments

@paradigm
Copy link

@paradigm paradigm commented Feb 25, 2021 •
edited

While I quite like the information readily provided by g:lsp_diagnostics_float_cursor and g:lsp_diagnostics_echo_cursor, their automatic nature doesn't fit my workflow.

Would it be difficult to add an avenue to trigger them on-demand, similar to <plug>(lsp-hover) / :LspHover?

Along similar lines, would it be difficult to add a g:lsp... setting to have <plug>(lsp-next-diganostic) and related items echo the diagnostic jumped to on the bottom line, similar to vim commands like :lnext?

Thanks!
@prabirshrestha
Copy link
Owner

@prabirshrestha prabirshrestha commented Feb 25, 2021

great idea! should be simple if you want to give it a try.

you will need to slightly refactor this file so we expose an internal api that plugin.vim can call.
@paradigm paradigm mentioned this issue Feb 25, 2021
Open
@stale
Copy link

@stale stale bot commented Apr 26, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@stale stale bot added the wontfix label Apr 26, 2021
@paradigm
Copy link
Author

@paradigm paradigm commented Apr 26, 2021 •
edited

I don't understand how we went good first issue that I could give a try, which I promptly did and have had an MR that was good to go two months ago which I have maintained against upstream to fix merge conflicts for those two months to wontfix.
@stale stale bot removed the wontfix label Apr 26, 2021
@stale
Copy link

@stale stale bot commented Jun 26, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@stale stale bot added the wontfix label Jun 26, 2021
@paradigm
Copy link
Author

@paradigm paradigm commented Jun 27, 2021

See you again in August, stale bot.
@stale stale bot removed the wontfix label Jun 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement good first issue
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@paradigm @prabirshrestha