Skip to content
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

Feature Request: More granular config printing options with ghostty +show-config #2486

Open
archcorsair opened this issue Oct 24, 2024 · 1 comment

Comments

@archcorsair
Copy link

archcorsair commented Oct 24, 2024

Current Behavior

Currently, running ghostty +show-config prints all the "changes-only" keys in the configuration. While helpful, this can be inconvenient if you're only interested in the value of a specific key.

Request

It would be beneficial to have more granular control over what configuration information is displayed. I propose the following:

  • Ability to specify a key: Allow users to specify a single configuration key to display its value
  • Option to show default values: Add the --default flag to display the default value of a given key

Example

# Show the current value of the 'font-family' key
ghostty +show-config font-family

# Show the default value of the 'font-size' key
ghostty +show-config font-size --default

Benefits

  • Usability: Makes it easier to quickly find the value of a specific configuration option
  • Debugging: Helps users identify discrepancies between their current configuration and the default settings
  • Clarity: Provides a more concise and focused output when inspecting configuration values
@jparise
Copy link
Collaborator

jparise commented Oct 24, 2024

I like the idea of being able to show the details for a single configuration key (or maybe also a list/pattern).

I was actually looking for something similar recently when I was considering adding a "look up the documentation for the configuration key under the cursor" command to our bundled vim plugin. This would make it pretty easy to implement that.

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

No branches or pull requests

2 participants