Tags: simonw/showboat
Tags
Fix parseImageInput to handle shell-escaped \! in markdown image refs (… …#22) Some shells escape "!" to "\!" even in single-quoted strings, causing the markdown image reference parser to fail to recognize the  syntax. The entire escaped string was then treated as a file path, producing the error "image file not found: \". Strip the leading backslash when the input starts with \. When a markdown reference is detected (starts with ![ and ends with )) the alt text and path are extracted. The image is copied with a generated filename and the alt text is preserved in the output. Plain paths continue to derive alt text from the generated filename. https://claude.ai/code/session_01TKxtWqAnWzSwgPdY23Zgx6 * Update README to reflect new image command interface https://claude.ai/code/session_01TKxtWqAnWzSwgPdY23Zgx6 --------- Co-authored-by: Claude <noreply@anthropic.com>
Use cog to auto-generate --help output in README (#9) * Use cog to auto-generate --help output in README Replace the manually maintained Usage/Global options/Exec output/Popping entries sections with a single cog block that runs `go run . --help` and embeds the full help text in a fenced code block. This keeps the README in sync with the actual CLI help output. https://claude.ai/code/session_011LqtVUFCcVLs2LBuvZZpFW * Move help text to embedded help.txt, use cog for README Extract the --help text from an inline Go string literal to help.txt, embedded at compile time via //go:embed. This makes the help text easier to maintain and eliminates backtick escaping workarounds. Add sections for Image, Verify, and Extract commands with details agents need (exit codes, --output flag, --filename flag). Add a concrete exit code example to the Exec section. The README now uses a cog block that runs `go run . --help` to generate the help text, keeping docs in sync with the actual binary output. https://claude.ai/code/session_011LqtVUFCcVLs2LBuvZZpFW * Fix help text example, add cog check to CI Update the resulting markdown format in help.txt to match the example: show python3 (not python) since the example pops the python exec and redoes it with python3, and include the image output. Add a CI step that runs `cog --check README.md` to catch cases where help.txt is updated but cog hasn't been re-run on the README. https://claude.ai/code/session_011LqtVUFCcVLs2LBuvZZpFW * Use four-backtick fence for help output in README The help text contains triple-backtick code blocks in its "Resulting markdown format" section, so the outer fence needs four backticks to render correctly. https://claude.ai/code/session_011LqtVUFCcVLs2LBuvZZpFW --------- Co-authored-by: Claude <noreply@anthropic.com>