What happened?
In the settings dialog (/settings command) changing a setting that requires app restart will persist that change across scopes in the UI (but only save to the active scope!). This means that a user cannot reliably edit restart required settings for multiple scopes and save them all at once.
For example, let's say you want respectGitIgnore to be true in user, false in workspace, and false in system. You cannot do that without multiple restarts.
What did you expect to happen?
I think that users should be able to go into the dialog and edit any setting for any scope in one fell swoop!
Client information
Client Information
Run gemini to enter the interactive CLI, then run the /about command.
> /about
# paste output here
Login information
No response
Anything else we need to know?
No response
What happened?
In the settings dialog (/settings command) changing a setting that requires app restart will persist that change across scopes in the UI (but only save to the active scope!). This means that a user cannot reliably edit restart required settings for multiple scopes and save them all at once.
For example, let's say you want respectGitIgnore to be true in user, false in workspace, and false in system. You cannot do that without multiple restarts.
What did you expect to happen?
I think that users should be able to go into the dialog and edit any setting for any scope in one fell swoop!
Client information
Client Information
Run
geminito enter the interactive CLI, then run the/aboutcommand.Login information
No response
Anything else we need to know?
No response