Adding further actions to compile context to pdf.

[davepwsmith]

My workflow (because of reasons to do with templating constraints, poetry and foreign languages) consists of me compiling from markdown --> context --> pdf.

This is reasonably easy, but I was wondering whether I could somehow get the pandoc workflows to do the context command for me too, since it's as simple as context $file && context -- purge && open $(basename $file .tex).pdf. Indeed, what would be really great would be if I could convince scrivener's compile feature to set all of this off via a watched folder, so that when I compiled my md, it was automatically converted to context/tex and then to pdf. Any ideas?

[fractaledmind]

Can you give me a bit detail about your current workflow right now, so that I can get a better sense of how Pandoctor might be able to simplify things?

Like, do you use Pandoctor in your workflow right now? Or not at all? If no, what is the limitation? Do the custom templates not provide enough flexibility to achieve your result? If not, why?

The more detail, the better.

[davepwsmith]

OK, so:

At present I save my file as a markdown file from scrivener, it's all written in Pandoc markdown. Then I run pandoctor, with a template, to create a .tex file, which I can compile in the terminal with the command context $file --purgeall. I was just wondering if there was an easy way to hook that extra command into the end of a pandoctor template (for example) so that I don't have to run it separately?

[fractaledmind]

This project is abandonware and I don't work on it any longer.