On 7/2/19 4:29 PM, Stephan Witt wrote:
> Am 02.07.2019 um 01:44 schrieb Richard Kimberly Heck <rikih...@lyx.org>:
>> -------- Forwarded Message --------
>> Subject: [ANNOUNCE] LyX 2.3.3
>> Date: Mon, 1 Jul 2019 16:44:12 -0500
>> From: Mauricio Andrade <guzmandr...@icloud.com>
>> To: rikih...@lyx.org
>>
>>
>> After updating to 2.3.3 I no longer can compile files on iCloud folders that
>> have paths like
>>
>> ~/Library/Mobile Documents/com~apple~CloudDocs/
>>
>> I get this error several times with a minimal file (only title and a line of
>> text):
>>
>> ! LaTeX Error: Missing \begin{document}.
>>
>> I’ll go back to 2.3.2 in the meanwhile.
>>
>> Thank you
>>
>> —
>> Mauricio Andrade
> Unfortunately I can reproduce the issue. One can test it w/o an iCloud folder.
> I’m not an user of iCloud - so I’ve made a directory with path
> "~/Library/My Mobile Documents/com~apple~CloudDocs" and placed a LyX document
> there. The exported tex files are the same with 2.3.2 and 2.3.3.
> I’m not sure if the tilde characters in the path name are the culprit.
>
> What happens on Linux with documents in such directory paths?
Same problem. I've traced it to:
\def\input@path{{/home/rikiheck/this~silly~dir/}}
It appears to be that LaTeX itself has problems with such paths. If we
add \detokenize:
\def\input@path{{\detokenize{/home/rikiheck/this~silly~dir/}}}
then it works.
In 2.3.2, we get:
\def\input@path{{/home/rikiheck/this\string~silly\string~dir/}}
This seems to be a regression in ac351f40f1d1. We used to call
support::latex_path here, but now only call os::latex_path, and the
result is that ~ doesn't get '\string'd. I would guess that there may be
similar problems with other characters that are handled there.
Note that this is also in master.
Riki
