tag:support.markedapp.com,2011-09-11:/discussions/problems/161942-pdflatex-not-foundMarked: Discussion 2021-02-24T06:25:52Ztag:support.markedapp.com,2011-09-11:Comment/490512082021-02-23T12:51:28Z2021-02-23T12:51:28Zpdflatex not found<div><p>First question: duress running pandoc with the exact arguments in marked work from the command line?</p>
<p>Second question: why are you outputting to PDF? Marked can't properly display PDF output.</p>
<p>Your PATH as you know it does not exist for a custom processor. It's run in a shell outside of your user. Is the path you specified for resources the one needed for pdflatex, or is it looking for it elsewhere? I do include /use/local/bin in the path, so you could install it there, or you could use a shell script that actually sourced your user files and then ran pandoc.</p>
<ul>
<li>Brett</li>
</ul></div>Bretttag:support.markedapp.com,2011-09-11:Comment/490512082021-02-23T15:20:26Z2021-02-23T15:20:27Zpdflatex not found<div><p>Dear Brett,</p>
<p>Thank you so much for your reply.</p>
<p>First: Yes, pandocs from the command line works except instead of the "-t pdf" argument I write "-o blabla.pdf".</p>
<p>Second: My whole problem is that when it produces the .md preview the .csl formatting does not appear correctly, so I thought forcing it into a pdf would produce the correct csl formatting. If you have another idea for producing the correct formatting I would really appreciate it!</p>
<p>I'm not sure I understand the last point exactly. If the custom processor doesn't rely on PATH where does it look for (and fail to find) pdflatex? I'm sorry I don't quite understand what you mean by a shell script that sources my user files and then runs pandoc. When I use a shell script to run pandoc I have no problem - the problem is when I try to use Marked 2...</p>
<p>Thanks so much for your help,<br>
Doron</p></div>Doron Shiffer-Sebbatag:support.markedapp.com,2011-09-11:Comment/490512082021-02-23T18:05:45Z2021-02-23T18:05:45Zpdflatex not found<div><p>Unfortunately I'm no expert with pandoc and have zero experience with<br>
the csl issue. Forcing into a PDF might fix formatting, but it will make<br>
Marked pretty useless. At that point you're better off just generating<br>
PDFs on the command line and viewing in Preview...</p>
<p>What I'm referring to with the shell script is not running on the<br>
command line, but rather writing a shell script and using it as the<br>
processor instead of pandoc. The shell script would set your path up<br>
using <code>export PATH=</code> commands, then calling pandoc. Input is passed to<br>
the script via STDIN, so you can just <code>cat|pandoc [arguments...]</code>. It<br>
provides the ability to manually set up the environment in the way that<br>
works from the command line. It sounds like that might be more trouble<br>
for you than it's worth, though.</p>
<p>I haven't heard from anyone else that there have been issues with<br>
formatting .csl in Marked, so either you have expectations that aren't<br>
feasible (e.g. exactly mimicking PDF output in HTML), or there are<br>
pandoc settings I'm just not familiar with and can't be of much help<br>
with.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/490512082021-02-24T06:25:50Z2021-02-24T06:25:51Zpdflatex not found<div><p>Dear Brett,</p>
<p>Got it - thanks so much for your assistance! It may be that my expectations are too high but I will also try to play around with the csl itself to see if that changes anything..</p>
<p>Best,<br>
Doron</p></div>Doron Shiffer-Sebba