Hacker News new | ask | show | jobs
by stack_framer 12 days ago
No, but this is a great suggestion. I imagine a flow that looks something like this:

(1) When creating the textile, you would add a step to "wait for new clipboard data."

(2) When you run the textile, and it gets to that step, a modal would appear, prompting you to copy the new thing to your clipboard.

(3) Once you've got the new thing on your clipboard, you would go back and click "Continue" on the modal from step 2.

(4) Textile would continue with the new thing on your clipboard.

Is that kind of what you were thinking?
1 comments
baliex 11 days ago
That’s exactly what I was thinking. And I think you’re saying the same thing, but to be sure: the _wait_ wouldn’t be a timer, it’d be watching the clipboard for changes and proceeding as soon as it changed.

If we’re going to do the discovery out in the open.. it would be nice to be able to specify the prompt as part of the Textile (e.g. “Copy the GitHub URL”). And then also showed the clipboard contents it is going to proceed with, before proceeding. A single key press (Enter?) would be ideal to proceed. That protects me from accidentally passing sensitive data through.

link
stack_framer 11 days ago
I like the idea of being able to specify the prompt, as a reminder of what you wanted to copy to the clipboard at that point.

I've created a new issue for this (it's similar to an idea I already had):

https://github.com/rob-johansen/textile/issues/75

link