Replies: 2 comments
-
ME TOO! If one command is inserting and running a templater script with a system.prompt, I want Commander to wait for the prompt to be answered and the script run before continuing to the next command. Answering might take much more than Commander's 10 second maximum delay. |
Beta Was this translation helpful? Give feedback.
0 replies
-
it would be great, especially if you have multiple commands building on each other.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have built some macros which run steps which require user input, and I want the script to pause execution until after the input is entered and the step completes. Currently, the next step begins as soon as the prompt appears.
This is my current workflow for publishing a page to micro.blog—Micro.publish appears to create a text buffer that isn't affected by the undo command, so a brief pause is all that is needed.
This macro is a bit more difficult:
If I place a long pause between steps 1 and 2 (about 5 seconds), the script works, but I need to click through the Longform steps before the pause ends, or the previous version of the compiled manuscript will be published.
The long pause works, but I'm wondering if there is a way to ensure the macro pauses until the entire previous step completes. How does Commander determine that the previous step has completed? Does Obsidian provide a standard communication method for plugins? I suspect not, given that you've provided the ability to add a delay.
Thanks,
kt
Beta Was this translation helpful? Give feedback.
All reactions