Allow MARKED_ORIGIN, etc., variable substitution in customprocessor arguments

Keith B.'s Avatar

Keith B.

15 Apr, 2021 11:43 PM

Yes, it's another pandoc-related suggestion… pandoc has a --resource-path option which allows you to explicitly specify where it should search for files. Setting --resource-path correctly solves about 90% of pandoc-related path problems. At the moment, though, if you specify --resource-path="$MARKED_ORIGIN" in the custom processor arguments this is passed through to pandoc as the literal string --resource-path="$MARKED_ORIGIN" with no variable substitution.

This can be worked around with a trivial wrapper script, but it would be tidier (and somewhat more user-accessible) to be able to use the environment variables in the GUI processor arguments.


  1. Support Staff 1 Posted by Brett on 17 Apr, 2021 07:05 PM

    Brett's Avatar

    I don't hate this idea, seems like a reasonable assumption that it would
    work. Will look into implementing it.


  2. Support Staff 2 Posted by Brett on 27 May, 2021 11:58 AM

    Brett's Avatar

    This is done for the next update release. All environment variables will
    be substituted when used as "$VARIABLE" in processor and preprocessor
    arguments. Thanks for the suggestion.


  3. 3 Posted by Keith B. on 27 May, 2021 01:02 PM

    Keith B.'s Avatar

    Awesome, thanks a bunch for implementing!

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac