Hi Liyu,

Could you tell me what the output of
(call-process "kpsewhich" nil (list standard-output nil) nil
                               "--expand-path" "{.,./.}")
is?  If that is ".;./.", we can use it to know the right path

Ikumi Keita

>>>>> Ikumi Keita <ik...@ikumi.que.jp> writes:
> Hi Liyu,
>>>>> Liyu Gong <liyu.g...@uky.edu> writes:
>> Sorry for multiple replies. But I just noticed that my cursor moves to
>> the next line after evaluation. So I guess there is a ".\n" inserted.

>> Thanks,
>> Liyu

>> On Sun, Apr 8, 2018 at 1:09 AM, Liyu Gong <liyu.g...@uky.edu> wrote:
>>> Hi Ikumi,
>>> After evaluation, there is only a dot inserted right at where I type "C-x 
>>> C-e".
>>> .
>>> Thanks,
>>> Liyu

> Thanks.  Hmm, strange result...  Here both texlive for freebsd and
> texlive for w32 don't remove ".." from the output, even when the current
> directory is the root directory.  When the result doesn't contain
> neither ":" nor ";", AUCTeX cannot know the right path delimiter.
> Sorry, let me think for for a while.

> Regards,
> Ikumi Keita

>>> On Sun, Apr 8, 2018 at 12:59 AM, Ikumi Keita <ik...@ikumi.que.jp> wrote:
>>>> Hi Liyu, thanks for your patience.
>>>>>>>>> Liyu Gong <liyu.g...@uky.edu> writes:
>>>>> Hi Ikumni,
>>>>> The result of the evaluation is: 1 (#o1, #x1, ?\C-a)
>>>> Ah, no, what I'd like to know is not the lisp return value, but the
>>>> string inserted in the buffer.  What string is inserted in the buffer
>>>> when you put the point just after the following form in *scratch* buffer
>>>> and type C-x C-e ?
>>>> (call-process "kpsewhich" nil
>>>> (list standard-output nil) nil
>>>> "--expand-path" "{.,..}")
>>>> I suspect that it is ".:..", not ".;..".  If this speculation is
>>>> correct, then cygwin version of kpsewhich is used at auto detection.
>>>>> Yes, I do have a cygwin version TeX distribution. But I just double
>>>>> checked. I didn't put the cygwin path in windows PATH, or in emacs
>>>>> exec-path.
>>>> Hmm.
>>>> Regards,
>>>> Ikumi Keita

bug-auctex mailing list

Reply via email to