Compile Step: Standard Obsidian commands

[tryonkus]

What should this step do?
Run an arbitrary Obsidian command

Should this step affect scenes, manuscripts, or join the two?
After the compile is finished, I'd like to be able to execute standard Obsidian commands on the compiled manuscript.

I'm using Commander to build basic macros, including Regex Pipeline to prepare text for publishing and micro.publish to publish to micro.blog. I can include a Longform command to compile the current project with the default workflow, which avoids any user input. I'm having issues with steps that do require user input—the macro doesn't know to wait until after the input is entered and the command is completed, so I need to estimate how long it will take and add a delay of X milliseconds.

The advantages to scripting in Longform would be:

• The script would execute as part of my compile process.
• I'm hoping Longform would handle step completion better (this could be a limit of the Obsidian API).
• I wouldn't have to write my own Javascript (getting there, but I've got some learning to do).

I'm guessing I can execute Obsidian commands from a Javascript user step, and the simple answer to this might be to point me to documentation of how to do that. I've learned enough JS to write fairly sophisticated Templater templates, and I could buckle down and learn enough to write a user step. 😏

Thanks for any suggestions you can provide.

[kevboh]

Yes, this is definitely a custom user step, the docs for which are here. I don't know off the top of my head how to call a command directly from the Obsidian API, but I think it's doable. I don't have time atm to actually write the step, but please let me know if you get stuck.