On 7/6/19 5:57 AM, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 03.07.2019, 15:53 -0400 schrieb Richard Kimberly Heck:
>> 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/}}
> Note that the \string solution does not work any longer with recent
> LaTeX.
>
>> 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.
> \detokenize is only omitted for ASCII characters, so it seems
> worthwhile to handle just that special case (and add others if it turns
> out to be necessary).
>
> Like in the attached patch.Fine by me. Riki
