gemini-cli - 💡(How to fix) Fix Standardize boolean settings to use consistent positive phrasing ("Show" instead of "Hide") [1 comments, 1 participants]

What would you like to be added?

<img width="1966" height="525" alt="Image" src="https://github.com/user-attachments/assets/bc281ad7-1438-41be-8294-aaa8cb4db6be" />

Currently, the application's configuration settings mix negative ("Hide") and positive ("Show") phrasing for boolean toggles.

For example, right next to each other, the settings display:

Hide Banner (Negative phrasing)

Show Line Numbers (Positive phrasing)

This mixed nomenclature creates a confusing user experience. Using negative phrasing for boolean toggles forces users to create mental double-negatives to achieve their desired configuration (e.g., having to set Hide Banner to false in order to show it). When scanning a list of settings, constantly switching between "true means on" and "true means off" introduces unnecessary cognitive load and increases the likelihood of misconfiguration.

Why is this needed?

Mixing positive and negative phrasing in configuration settings is a recognized UX anti-pattern. When a user encounters a negatively phrased setting like Hide Banner, they are forced to parse a mental double-negative to turn the feature on (e.g., "I must set hide to false to show the banner").

When scanning a long list of options, this inconsistency forces the user to constantly switch their mental model between "true means enabled/visible" and "true means disabled/hidden." Standardizing purely on positive phrasing—where true consistently means a feature or UI element is active—drastically reduces cognitive load, minimizes user configuration errors, and aligns the settings menu with industry-standard UI/UX best practices.

Additional context

No response