Home → Questions →

All should be well, but no custom pdf is produced

• Edit

RHvdG

16 Mar, 2025 05:01 PM

Hi,
I am testing Marked 2, using the trial version. In the settings, I have entered the path to pandoc and the arguments I used in Terminal to produce Tufte style articles:

--pdf-engine=xelatex -V lang=nl -V papersize:a4 -V documentclass:tufte-book -V mainfont:ETbb.otf -o "{OUT}" "{IN}"

The "{OUT}" "{IN}" is what I think is needed for Marked 2. As the screenshot shows, pandoc is present. But how to proceed? The Export options don't include a "PDF (Custom Processor)" option. I did enable the custom processor for the document, and the traffic light is green. But I get just the preview style in PDF.

A pointer would be appreciated.

• Screenshot_2025-03-16_at_17.49.05.png 462 KB

1. 1 Posted by RHvdG on 19 Mar, 2025 08:46 AM

   

   Two days later, no response. Luckily, adding this to my .vimrc gave me most of what I needed from Marked in MacVim:

   function! PandocExport() let filename = expand('%:r') execute '!pandoc --pdf-engine=xelatex -V lang=nl -V papersize:a4 -V documentclass:tufte-book -V mainfont:ETbb.otf -o "' . filename . '.pdf" "%"' endfunction nnoremap <leader>pp :call PandocExport()<CR>

   • Edit

2. Support Staff 2 Posted by Brett on 25 Mar, 2025 03:32 PM

   

   Marked doesn't have a custom PDF export option. Not sure where you got {out} and {in} from, but Marked handles all input and output on STDIN and STDOUT, you can't specify files.

   PDF rendering is done using the WebKit engine. If the preview is generated with Pandoc, then the results of that custom processor will be used to generate the PDF (via WebKit), but Pandoc will not be used.

   • Edit

3. Brett closed this discussion on 25 Mar, 2025 03:32 PM.