[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [AUCTeX-devel] Fix about usage of kpsewhich

From: Ikumi Keita
Subject: Re: [AUCTeX-devel] Fix about usage of kpsewhich
Date: Sun, 03 Dec 2017 15:27:36 +0900

Hi David and all,

>>>>> David Kastrup <address@hidden> writes:
>>> I just thought of another approach using brace expansion.  We can obtain
>>> the right path delimiter by just taking the second character of the
>>> output of "kpsewhich --expand-path {.,..}".
>> Presumably
>> kpsewhich --expand-path "{.,..}"
>> That's really clever.  Yes, it should do the trick, assuming the Windows
>> executable doesn't try to be helpful by inserting the current directory,
>> and "foreign" implementations of kpsewhich (like the MikTeX one) behave
>> accordingly.

> Ok, here is how I suggest to use that trick: if the expanded string
> contains ; use ; as delimiter, otherwise :.  That should work even if
> some executable considers it sane to insert drive letters or directory
> separators or whatever else.  But a ; in there should never be
> accidental.

Thanks, I took in your suggestion to create the attached patch.  I
checked that it also passes the regression tests.  If nobody objects, I
will commit it to the git repo.

Ikumi Keita

Attachment: brace-expansion-trick
Description: check semicolon in the output

reply via email to

[Prev in Thread] Current Thread [Next in Thread]