Hello, Stig Brautaset <s...@brautaset.org> writes:
> And, indeed, running pdflatex on that file works perfectly fine from the > shell: > > #+BEGIN_EXAMPLE > 17:37:57 /tmp> /Library/TeX/texbin/pdflatex ~/Org/TODO.tex > This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015) (preloaded > format=pdflatex) > restricted \write18 enabled. > entering extended mode > (/Users/stig/Org/TODO.tex > LaTeX2e <2015/01/01> > > [...] > > Output written on TODO.pdf (10 pages, 206446 bytes). > Transcript written on TODO.log. > #+END_EXAMPLE > > > ... except if you use the full path (rather than the symlink), in which case > pdflatex chockes on the filename: > > #+begin_example > 17:27:25 /tmp> pdflatex "/Users/stig/Library/Mobile > Documents/com~apple~CloudDocs/Org/TODO.tex" > This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015) (preloaded > format=pdflatex) > restricted \write18 enabled. > entering extended mode > ! I can't find file `"/Users/stig/Library/Mobile Documents/com"'. > <to be read again> > \protect > <*> "/Users/stig/Library/Mobile Documents/com~ > apple~CloudDocs/Org/TODO.tex" Indeed. It seems pdflatex doesn't like the ~ sign excepted at the beginning of the filename. It doesn't seem to be Org related though. In any case, I'm wondering if we really need to send the full canonical path (as returned by `file-truename') of the tex file to the pdflatex process. For example, we could set `default-directory' to the directory of the tex file and provide only relative filename with %f. If needed, %F may be used for the full path. I don't think it would introduce incompatibilities. WDYT? Regards, -- Nicolas Goaziou
