Document interrupt-key split in /help and NEWS#82
Merged
Conversation
The interrupt key splits cleanly by environment but neither path's /help mentioned it: RStudio console + corteza::chat() uses Esc (RStudio swallows Ctrl+C for clipboard copy), while the terminal ~/bin/corteza CLI uses Ctrl+C (terminals send a raw ^[ byte for Esc, which is not a signal). NEWS originally implied Esc works in both environments and Ctrl+C falls back to the CLI; reality is that each environment has exactly one usable interrupt key and they don't overlap. Add a Keys: section to both /help outputs and tighten the NEWS bullet.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Keys:section to both/helpoutputs and tighten the NEWS bullet.corteza::chat(): Esc only — RStudio swallows Ctrl+C for clipboard copy.~/bin/corteza: Ctrl+C only — terminals send a raw^[byte for Esc, not a signal.Earlier NEWS implied Esc worked in both and Ctrl+C was a CLI-only fallback. Wrong on both counts; each environment has exactly one usable key and they don't overlap. Troy caught this on a smoke test.
Test plan
corteza::chat()→/help. Confirm newKeys:section reads correctly.corteza --help. Same.Notes
Making terminal Esc into a SIGINT is doable (raw mode + bare-ESC timeout disambiguation so arrow-key sequences don't kill the process) but a separate project — filed for the QOL list, not in scope here.