Light Mode

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

docs: add reference to default options list#680

Open
hesreallyhim wants to merge 5 commits intocharmbracelet:mainfrom
hesreallyhim:docs/add-reference-to-default-options-list
Open

docs: add reference to default options list#680
hesreallyhim wants to merge 5 commits intocharmbracelet:mainfrom
hesreallyhim:docs/add-reference-to-default-options-list

Conversation

Copy link

hesreallyhim commented Nov 29, 2025 *
edited
Loading

  • I have read CONTRIBUTING.md.
  • [-] I have created a discussion that was approved by a maintainer (for new features). (docs-only)

I found myself looking through the code to find the default values for various Options settings, so I thought it would be helpful to provide the user with a list of these settings in the README. So as to make the smallest visible change to the existing docs, I added a link in the README to a new Markdown table I assembled (with LLM assistance) based off of the info in vhs.go and related files like styles.go.

If you want to "check my work" there is a file in 037d437 which contains a CSV file I built up to compile the information including line references for the different settings.

Thanks, this library is amazing!

(Partially?) Fixes: #638
(Partially?) Fixes: #495 (duplicate)

hesreallyhim requested a review from a team as a code owner November 29, 2025 20:40
hesreallyhim requested review from aymanbagabas and kujtimiihoxha and removed request for a team November 29, 2025 20:40
hesreallyhim mentioned this pull request Nov 29, 2025
Copy link
Contributor

joshka commented Nov 29, 2025

I think that ideally, the setting, description and default should be in the same table where possible.

hesreallyhim reacted with thumbs up emoji

Copy link
Author

hesreallyhim commented Nov 29, 2025

I think that ideally, the setting, description and default should be in the same table where possible.

I just did it this way for minimal disturbance to the main README.

Copy link
Contributor

joshka commented Nov 29, 2025

I just did it this way for minimal disturbance to the main README.

The problem I had with this to start is that you have to look in two places for the information. This simplifies the two places, but it remains at two. The 'what is the default' question is now answered by:

  1. look at readme
  2. search 'default' in readme
  3. click and read other doc, flipping back to readme for docs.

Copy link
Author

hesreallyhim commented Nov 29, 2025 *
edited
Loading

@joshka maybe I could put the defaults table inside a disclosure element. I'm open to whatever, and totally respect your opinion but also want to hear from a codeowner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

aymanbagabas Awaiting requested review from aymanbagabas aymanbagabas is a code owner automatically assigned from charmbracelet/everyone

kujtimiihoxha Awaiting requested review from kujtimiihoxha kujtimiihoxha is a code owner automatically assigned from charmbracelet/everyone

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Document the defaults for each setting / command Show the defaults for each setting in the docs and the docs tape file

2 participants