Excellent, this now works perfectly. I'm not sure if it is a bash vs zsh difference, as I am using the latter in my terminal. But what matters it is now working. Thank you.

Thanks, Ian. I'll do that. If I find a way to automate the creation of output using the post-processor, I'll come back and share.

Many thanks, Ian, for the help. You pointed me in the right direction, but to get it to work, I had to make a couple of modifications: 1. putting <$inputfile> in quotes threw up an error. 2. 2>&1 >> output.log produced an empty log. What worked for me was: Arguments: -drefs -dlatex -dpdf-xelatex...

Hello. I have successfully set up the post-Processing pane to execute Pandoc. I am trying to use Pandoc with the defaults: Path: /usr/local/bin/pandoc Arguments: -drefs -dlatex -dpdf-xelatex <$inputfile> -o <$outputname>.pdf Environment: /library/tex/texbin:/Users/NAME/.local/share/pandoc/ However, ...

Thanks, Ian. Yes I have this working fine. What I'm trying to figure out is if there is a way to dispense with the local Makefile, and just have Scrivener output everything needed to then call upon the main Pandoc-scholar makefile. A bit like how using your Scrivomatic doesn't require a pre-existing...

Thanks for your help, Ian. Yes, the make command is working from the terminal. I realise now that I should have mentioned: I am working on an M1 MacBook Air. Apparently (on my machine at least), the make command does not work with this newer architecture, but only if I prepend the make command as su...

Hello. I wonder whether anyone could help me set up Scrivener's processor settings in Compile to use Pandoc Scholar. What I've done so far: * I've downloaded and installed the Pandoc Scholar directory (pandoc-scholar-main) into ~/.local/share * I've added this directory into my ~/.bash_profile * In ...

I'd like to second the request. As much as I try to various colour combinations, the highlighting of footnotes in the inspector (full screen or otherwise) when you click on a footnote marker in the editor could be contrasted better with surrounding colours

It does indeed (though everything still needs to be re-arranged manually, which happily is a one-off affair). Perhaps this could be forwarded to the relevant bug-department. Thank you for the quick reply and solution.

I accidentally pressed on "key" at the top of the Compile > Metadata pane, when compiling for MultiMarkdown. Now, all of my metadata fields are sorted alphabetically. There is a small arrow now appearing to the right of the word "key". I need to be able to sort the keys manually,...

For the record, there is a solution for this after all. What must be commented out are the symbols #, @ and $@ with a backslash before each. e.g. <\#page:\$@> e.g. <\@page:\$@> e.g. \!ar\<id> (Note that in the final example a backslash is also required before the < symbol.) When the Scrivener projec...

Thank you both for your suggestions. I am documenting how I have set up Scrivener + Pandoc (with all of its filters, custom templates, etc.) for my form of academic writing, in case I ever to have to set it up again. This includes a list of my replacements and how they work. I have indeed tried all ...

Thank you for your response and help. Unfortunately, simply putting a backslash is having no effect in this instance. The commands are still being replaced during compilation.

Hello. I am trying to escape a replacement command — !fig<$@> — so that it survives compilation unchanged.

I know that you can escape placeholder tags by placing a back-slash before the opening < symbol, and am looking for the equivalent for replacements. Thank you.

liz wrote:They're also extremely useful for academic writing with a lot of internal references, since you can make a replacement in the Compile dialog that converts the Scrivener link syntax to the internal reference syntax in MMD or LaTeX.

@liz, could you kindly explain how you do so?