Skip to content

Give crispctl a conventional help screen and uuid selectors - #107

Merged
didriksg merged 1 commit into
mainfrom
crispctl-help
Sep 2, 2026
Merged

Give crispctl a conventional help screen and uuid selectors#107
didriksg merged 1 commit into
mainfrom
crispctl-help

Conversation

@didriksg

@didriksg didriksg commented Sep 2, 2026

Copy link
Copy Markdown
Owner

The help text read like a man page pasted into a terminal: full invocations under a heading, then four paragraphs. It now prints what every comparable tool prints: a usage line, an aligned command table with one-line descriptions, and a short footer with the output format and exit codes. The long explanations live in the README section, which already said most of it.

Two changes ride along, both cheap while nothing has shipped. displays list becomes display list, so every command uses the same singular noun as the display commands in #97. And brightness get and brightness set take a uuid as well as a runtime id, through a selector field the app resolves id first, then uuid in any case. The numeric display field still works for clients that already send it. The resolver matches the one in #97 so that PR can adopt it on rebase.

Verified live on the Dell U2412M: get and set by id and by uuid in both cases, unknown selectors refused with exit 3, the old command name rejected with the usage line.

🤖 Generated with Claude Code

https://claude.ai/code/session_016NDzD18GySiCwEGfWJiT4J

The help text read like a man page pasted into a terminal: full invocations under a heading, then four paragraphs. It now prints what every comparable tool prints, a usage line, an aligned command table with one-line descriptions, and a short footer with the output format and exit codes. The long explanations live in the README section, which already said most of it.

Two changes ride along, both cheap while nothing has shipped. `displays list` becomes `display list`, so every command uses the same singular noun as the display commands proposed in #97. And `brightness get` and `brightness set` take a uuid as well as a runtime id, through a `selector` field on the request that the app resolves id first, then uuid in any case; the numeric `display` field still works for clients that already send it. The resolver is written to match #97's, so that PR can adopt it on rebase.

Verified live on the Dell U2412M: get and set by id, by uuid in both cases, unknown selectors refused with exit 3, and the old command name rejected with the usage line.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016NDzD18GySiCwEGfWJiT4J
@didriksg
didriksg merged commit 01767be into main Sep 2, 2026
1 check passed
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

Successfully merging this pull request may close these issues.

1 participant