octoscope 0.41.1 — a flag stays a flag

The docs say flags override the config file for that run. They also ended up in the file. Start octoscope with --theme amber, pin a repository, and amber was your theme from then on. Same for --refresh, --compact, --public-only and --no-sponsor: the next save about anything else wrote them all.

I measured it before touching anything: four flags, then p twice (public-only on and off again, so a net change of nothing), and the config held all four.

Now a flag is for the run it is given to. If you change a setting in the app, in the settings panel or with p, that is a choice and it is saved. A flag you never touched is not.

Second fix: q quits on the launch screen. Before the first dashboard, a comma opened the settings panel behind the launch screen, and the next q went to a panel you could not see. Until there is a dashboard the screen now takes q, the help and rate-limit overlays, and a tab chosen ahead. Nothing else.

One thing you may notice: if you used a flag once to set something for good, it no longer sticks. Change that row in the settings panel instead.

The detail I enjoyed getting right: what counts as a choice. Saving the settings panel does not write everything it shows, only the rows you changed. Otherwise a run started with --public-only for a screenshot would make it permanent the moment you saved a new refresh interval.

Upgrade:

brew upgrade gfazioli/tap/octoscope

Do you expect a command-line flag to be remembered, or forgotten when the program exits?