Skip to content
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

Better conversion to quickfix list #3356

Open
Natr1x opened this issue Nov 7, 2024 · 0 comments
Open

Better conversion to quickfix list #3356

Natr1x opened this issue Nov 7, 2024 · 0 comments
Labels
enhancement Enhancement to performance, inner workings or existent features

Comments

@Natr1x
Copy link

Natr1x commented Nov 7, 2024

Is your feature request related to a problem? Please describe.
I would like to be able use telescope to filter my quickfix and location list but a lot of information is lost when sending to the quickfix list.
Diagnostics will for example discard end_lnum and end_col.

Describe the solution you'd like
Ideally I would like the action of sending entries to the quickfix list or location list to send all compatible fields of the entry.
I e if the entry has an end_lnum field then that would be copied to the quickfix entry.

I am unsure if valid and vcol should be copied directly however or some new field name should be introduced for them.

Lastly the whole entry would then be placed as is inside user_data. This way you would not lose any entry information when sending it to the quick.

Describe alternatives you've considered
An alternative solution would be to add something like an "telescope_entry_source_id" field to the user_data.

This would give plugins which want to make use of both telescope and the quicklist to handle quicklist entries differently depending on where they came from. I e If it is known that a quickfix entry was added by telescope from diagnostics then a plugin could retreive end_lnum and end_col and add them back themselves.

This would make on the fly usage a more complicated though since you wouldn't be able to just loop through and inspect the user_data but instead look up the documentation on a case by case basis.

@Natr1x Natr1x added the enhancement Enhancement to performance, inner workings or existent features label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement to performance, inner workings or existent features
Projects
None yet
Development

No branches or pull requests

1 participant