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?

Same on Android, duck browser

Thanks! Should be fixed.

I'm not too familiar with Espanso, but Textile is not a text expander. Textile allows you to pre-define a sequence of steps that dynamically generate the text you want, by running commands on your computer, reading your clipboard, or using hard-coded text you provide.

Here's a quick example, and one that I often use with Textile to generate a preview URL based on my current branch:

(1) Start with the output of the command `git branch --show-current` in the `~/code` directory (yielding text like `JIRA-1234/some-feature`).

(2) Replace all `/` characters with `-` (now the text is `JIRA-1234-some-feature`).

(3) Prepend `[preview](https://staging-`, which is the start of a markdown link (now the text is `[preview](https://staging-JIRA-1234-some-feature`).

(4) Append `.example.com)`, which is the end of the markdown link (now the text is `[preview](https://staging-JIRA-1234-some-feature.example.com)`).

(5) Copy the result to my clipboard.

With those steps saved in Textile, I can now click a button to run them over and over again (or use a keyboard shortcut if I assigned one). So no matter which branch I'm on, I'll always get a proper preview link without having to construct it manually myself.