feat(capture): add Capture Clipboard - #11
Merged
Merged
Conversation
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
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.
Why
Capture Selection needs text selected in the frontmost app. Often the text is already on the clipboard. Capture Clipboard sends it to a capture choice in one step.
What changed
capture-clipboard, with its own Capture Choice preference that uses the same wording as Capture Selection's.src/capture-clipboard.tsreadsClipboard.readText(). Empty or whitespace-only text shows a "Clipboard is empty" failure toast. Any other text goes to the sharedcapture().Scope
Plain text only. No HTML or image handling. The text is sent as copied, with no trimming.
Verification
pnpm lint,pnpm test(73 passed),npx tsc --noEmit, andpnpm buildpass.pnpm e2e:protocol: all 12 passed, run from the main checkout because the script reads the vault next to itself.Output/Inbox.mdis unchanged). The toast and byte-for-byte checks still need a run.