You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Often, I'd like to locate a reference/token/concept in a code-base and am only looking for file granularity. Because I'm searching file contents, I use :Telescope live_grep, but often, the sort algorithm puts 10's of entries from the same file in a row, making it difficult to browse usages in various files. I'm not picky about which usage from a file is displayed (first might be fastest but will usually just be imports, last might be slower, but more likely to be real usage); either seem usable.
Describe the solution you'd like
An option for pickers like {max_results_per_file} (number).
Describe alternatives you've considered
I have not explored other alternatives, and would be happy to hear any way these sorts of workflows can be supported with existing opts/commands.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Often, I'd like to locate a reference/token/concept in a code-base and am only looking for file granularity. Because I'm searching file contents, I use
:Telescope live_grep
, but often, the sort algorithm puts 10's of entries from the same file in a row, making it difficult to browse usages in various files. I'm not picky about which usage from a file is displayed (first might be fastest but will usually just be imports, last might be slower, but more likely to be real usage); either seem usable.Describe the solution you'd like
An option for pickers like
{max_results_per_file} (number)
.Describe alternatives you've considered
I have not explored other alternatives, and would be happy to hear any way these sorts of workflows can be supported with existing opts/commands.
The text was updated successfully, but these errors were encountered: