-
-
Notifications
You must be signed in to change notification settings - Fork 836
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
Updated docs to clarify which telescope.defaults options can be overriden by pickers #3251
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies for the very late response.
I have a few suggestions but otherwise looks good.
@@ -106,18 +106,26 @@ local telescope = {} | |||
--- pickers = { | |||
--- -- Default configuration for builtin pickers goes here: | |||
--- -- picker_name = { | |||
--- -- picker_config_key = value, | |||
--- -- default_config_key = value_one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
--- -- default_config_key = value_one | |
--- -- default_config_key = value_one, -- optionally override any default options |
--- of the options you want to use. Pickers have their own specific set of | ||
--- options, but also accept a subset of the defaults options. The default | ||
--- options which are valid to configure a picker are marked as | ||
--- "Picker-Overridable" in telescope.setup.defaults |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It'll probably be easier to mark options that aren't "picker-overriable".
In theory, all but a small handful can at least in technically be overriden by the each individual picker.
I would reword this bit slightly and let's leave out the marking of individual options an "Picker-Overridable" for now.
--- -- Options set here will be applied everytime you call this builtin | ||
--- -- picker. Each entry accepts a subset of the "defaults" configuration | ||
--- -- options, as well as the picker's own specific configuration options. | ||
--- -- Defaults options that are also valid for pickers are marked as | ||
--- -- "Picker-Overridable" in telescope.setup.defaults. Learn about one | ||
--- -- picker's specific set of options at telescope.builtin.$PICKER_NAME |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
--- -- Options set here will be applied everytime you call this builtin | |
--- -- picker. Each entry accepts a subset of the "defaults" configuration | |
--- -- options, as well as the picker's own specific configuration options. | |
--- -- Defaults options that are also valid for pickers are marked as | |
--- -- "Picker-Overridable" in telescope.setup.defaults. Learn about one | |
--- -- picker's specific set of options at telescope.builtin.$PICKER_NAME | |
--- -- Options set here will be applied everytime you call this builtin | |
--- -- picker. The pickers will also inherit the "default" options unless | |
--- -- they are overwritten. | |
--- -- See `:h telescope.builtin` for options unique to each picker. |
Description
Fixes #3238
The documentation isn't very clear about what keys are valid for pickers config options. There is a subset of of defaults options that pickers can override and it's not clear which ones are.
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list relevant details about your configuration
make test
make lint
Configuration:
Neovim version (nvim --version): NVIM v0.10.1
Operating system and version: Debian 12
Checklist: