-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Global setting to enable all shell integrations for a given shell #2023
Comments
Is it common enough that a user would like to disable all shell integrations? I would imagine that the common case is that you want to disable specific ones. |
This is also my case for most programs I have enabled. |
Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. Please read the relevant sections below before commenting. If you are the original author of the issue
If you are not the original author of the issue
Memorandum on closing issuesIf you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort. |
This is in my todo-list |
Issue description
Taken from #1809 (comment).
The change is quite simple but tedious:
programs.fish.enableAllIntegrations
(option name to be revisited).enable${SHELL}Integrations
's default value to that ofprograms.${SHELL}.enableAllIntegrations
i.e.default = config.programs.${SHELL}.enableAllIntegrations
.The last step is the tedious one because they are many instances of
enable${SHELL}Integrations
in the config.The text was updated successfully, but these errors were encountered: