GNU bug report logs -
#31079
Windows - Emacs-25.3.1 Can't find source.tex file
Previous Next
Reported by: Liyu Gong <liyu.gong <at> uky.edu>
Date: Fri, 6 Apr 2018 19:13:02 UTC
Severity: normal
Tags: notabug
Done: Arash Esbati <arash <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #143 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Ikumi,
You are right! One of my emacs init files modifies the exec-path and
env PATH and injects cygwin path to them. After remove the path or
re-order them, the problem disappears. So it is not a bug.
I sincerely apologize for wasting your valuable time on the false
alarm. Thank you so much for the kind help.
Best wishes,
Liyu
On Sun, Apr 8, 2018 at 10:00 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
> Hi Liyu,
>
>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>> Hi Ikumi,
>> The results is: "c:/cygwin64/bin/kpsewhich.exe" !!!!!!!!!
>
>> Sorry, I must messed up somewhere in my system. Thank you so much!
>
> In your message of Apr 7 with Message-ID:
> CAEL_qGyHPJqFyWi0GNKwACdOmWZLpzLwHcue14eyL70eryAPkg <at> mail.gmail.com
> , you wrote
>
>> I do have cygwin installed, so I tried add the following two lines in my init.el
>
>> (setenv "PATH" (concat "C:\\cygwin64\\bin;C:\\cygwin64\\lib;" (getenv "PATH")))
>> (setq exec-path (append '("C:/cygwin64/bin" "C:/cygwin64/lib") exec-path))
>
> Maybe these lines still remain in your init.el.
>
> And it seems that kpsewhich binary of cygwin discards ".." from the
> output of "kpsewhich --expand-path {.,..}", unlike other OSes.
>
> Best,
> Ikumi Keita
This bug report was last modified 2 years and 361 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.