Skip to content

Conversation

@davvid
Copy link

@davvid davvid commented May 17, 2025

Promote the "temp__scrolling_limit" option into an officially supported
configuration field that controls the number of results displayed by pickers.

Closes: #2779

Copy link

@alerque alerque left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this option be documented somewhere?

Promote the "temp__scrolling_limit" option into an officially supported
configuration field that controls the number of results displayed by pickers.

Closes: nvim-telescope#2779
@davvid
Copy link
Author

davvid commented Dec 12, 2025

@alerque thanks for considering this enhancement. I rebased and added a commit that documents this option. Let me know if there's a better place to document it.

BTW, from re-reading the code, it could be argued that max_results would be a better name for this option. max_results is the same name as the actual self.max_results field that opts.scrolling_limit gets assigned to, so it might be clearer to name them consistently.

I can add another commit to rename the field if this is being considered for merging and you agree that it's worth changing that detail. The current name came from removing the temp__ prefix from the original variable's name. I didn't think about it too much at the time. cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The default maximum result display count seems to have been mistakenly set to 250

2 participants