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.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 31079 in the body.
You can then email your comments to 31079 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Fri, 06 Apr 2018 19:13:03 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Liyu Gong <liyu.gong <at> uky.edu>:
New bug report received and forwarded. Copy sent to
bug-auctex <at> gnu.org.
(Fri, 06 Apr 2018 19:13:04 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi,
I installed AucTeX (Windows, Emacs-25.3.1) from elpa.gnu.org, but was
not able to successfully compiled the attached simple LaTeX file. The
error says:
ERROR: I can't find file `aa.tex'.
--- TeX said ---
! I can't find file `aa.tex'.
--- HELP ---
TeX can't find a file that it needs. If the name of the missing file
has the extension tex, then it is looking for an input file that you
specified---either your main file or another file inserted with an
\input or \include command. If the missing file has the extension sty
, then you have specified a nonexistent document style or style
option.
I tried to downgraded AucTeX, and it turned out that AucTeX-11.91.0
worked normally, any version that newer than 11.91.0 got the same
error.
Thanks,
Liyu Gong
[aa.tex (application/octet-stream, attachment)]
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 10:36:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu,
>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
> Hi,
> I installed AucTeX (Windows, Emacs-25.3.1) from elpa.gnu.org, but was
> not able to successfully compiled the attached simple LaTeX file. The
> error says:
> ERROR: I can't find file `aa.tex'.
> --- TeX said ---
> ! I can't find file `aa.tex'.
> --- HELP ---
> TeX can't find a file that it needs. If the name of the missing file
> has the extension tex, then it is looking for an input file that you
> specified---either your main file or another file inserted with an
> \input or \include command. If the missing file has the extension sty
> , then you have specified a nonexistent document style or style
> option.
Unfortunately, it doesn't seem to reproduce on my side. I tested with
emacs 25.2 on windows 10 and AUCTeX 12.1.1 from elpa. The file you
provided just compiles smooth with the file name "aa.tex".
Running `LaTeX' on `aa' with ``pdflatex -file-line-error -interaction=nonstopmode "\input" "aa.tex"''
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/W32TeX) (preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
LaTeX2e <2017-04-15>
Babel <3.15> and hyphenation patterns for 84 language(s) loaded.
(./aa.tex (c:/texlive/2017/texmf-dist/tex/latex/base/article.cls
...
Output written on aa.pdf (1 page, 84758 bytes).
Transcript written on aa.log.
TeX Output finished at Sat Apr 7 18:42:46
Does anyone else experience the same problem with Liyu?
> I tried to downgraded AucTeX, and it turned out that AucTeX-11.91.0
> worked normally, any version that newer than 11.91.0 got the same
> error.
I have no idea currently why such version dependency exists, since the
newest version 12.1.1 works without problem on my side.
Additional information might be helpful, e.g.
- The output of M-x TeX-submit-bug-report
- The content of the process buffer (displayed by C-c C-l)
- The path name of directory where aa.tex is saved
- The type and year of your TeX distribution
- Whatever you think might be clue to resolve this issue
Best regards,
Ikumi Keita
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 10:53:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu and Ikumi,
Here: Windows 7 32-bit, Emacs 25.3.1, and AUCTeX 12.1.1 from elpa, and the file compiles smoothly for me too. I have no clue where the problem could be. Maybe problems with quotes and spaces in the path name, combined with a customized tex command? Liyu, it'd be useful if you shared the additional debugging info that Ikumi suggested
> Additional information might be helpful, e.g.
> - The output of M-x TeX-submit-bug-report
> - The content of the process buffer (displayed by C-c C-l)
> - The path name of directory where aa.tex is saved
> - The type and year of your TeX distribution
> - Whatever you think might be clue to resolve this issue
Cheers,
J
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 13:58:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu,
The command call is just as mine, but I don't get any problem. It seems the problem is with tex-live rather than auctex.
If you open a command prompt at D:\ and run the simple command
pdflatex aa.tex
then does the problem persist?
Is your tex-live installed in the same partition (D:) as your tex file?
Cheers,
J
On 2018-04-07 15:30, Liyu Gong wrote:
> Hi guys,
>
> Thank you very much for looking into it. My system environment is as follows
>
> aa.tex is at D:/aa.tex
>
> OS: Windows 10 Home
>
> Emacs: GNU Emacs 25.3.1 (x86_64-w64-mingw32) of 2017-09-26, which is
> downloaded from the official gnu ftp site
>
> TeX distribution: texlive-2017
>
> Output of M-x TeX-submit-bug-report:
>
> Emacs : GNU Emacs 25.3.1 (x86_64-w64-mingw32)
> of 2017-09-26
> Package: 12.1.1
>
> current state:
> ==============
> (setq
> AUCTeX-date "2018-03-20"
> window-system 'w32
> LaTeX-version "2e"
> TeX-style-path '("~/.emacs.d/auctex"
> "d:/.emacs.d/elpa/auctex-12.1.1/style" "d:/.emacs.d/auctex/auto"
> "d:/.emacs.d/auctex/style" "auto" "style")
> TeX-auto-save t
> TeX-parse-self t
> TeX-master nil
> TeX-command-list '(("TeX" "%(PDF)%(tex) %(file-line-error)
> %(extraopts) %`%S%(PDFout)%(mode)%' %t" TeX-run-TeX nil
> (plain-tex-mode ams-tex-mode texinfo-mode) :help
> "Run plain TeX")
> ("LaTeX" "%`%l%(mode)%' %t" TeX-run-TeX nil
> (latex-mode doctex-mode) :help "Run LaTeX")
> ("Makeinfo" "makeinfo %(extraopts) %t"
> TeX-run-compile nil (texinfo-mode) :help "Run Makeinfo with Info
> output")
> ("Makeinfo HTML" "makeinfo %(extraopts) --html %t"
> TeX-run-compile nil (texinfo-mode) :help "Run Makeinfo with HTML
> output")
> ("AmSTeX" "amstex %(PDFout) %(extraopts)
> %`%S%(mode)%' %t" TeX-run-TeX nil (ams-tex-mode) :help "Run AMSTeX")
> ("ConTeXt" "%(cntxcom) --once --texutil
> %(extraopts) %(execopts)%t" TeX-run-TeX nil (context-mode) :help "Run
> ConTeXt once")
> ("ConTeXt Full" "%(cntxcom) %(extraopts)
> %(execopts)%t" TeX-run-TeX nil (context-mode) :help "Run ConTeXt until
> completion")
> ("BibTeX" "bibtex %s" TeX-run-BibTeX nil t :help
> "Run BibTeX") ("Biber" "biber %s" TeX-run-Biber nil t :help "Run
> Biber")
> ("View" "%V" TeX-run-discard-or-function t t :help
> "Run Viewer") ("Print" "%p" TeX-run-command t t :help "Print the
> file")
> ("Queue" "%q" TeX-run-background nil t :help "View
> the printer queue" :visible TeX-queue-command)
> ("File" "%(o?)dvips %d -o %f " TeX-run-dvips t t
> :help "Generate PostScript file")
> ("Dvips" "%(o?)dvips %d -o %f " TeX-run-dvips nil
> t :help "Convert DVI file to PostScript")
> ("Dvipdfmx" "dvipdfmx %d" TeX-run-dvipdfmx nil t
> :help "Convert DVI file to PDF with dvipdfmx")
> ("Ps2pdf" "ps2pdf %f" TeX-run-ps2pdf nil t :help
> "Convert PostScript file to PDF")
> ("Glossaries" "makeglossaries %s" TeX-run-command
> nil t :help "Run makeglossaries to create glossary file")
> ("Index" "makeindex %s" TeX-run-index nil t :help
> "Run makeindex to create index file")
> ("upMendex" "upmendex %s" TeX-run-index t t :help
> "Run upmendex to create index file")
> ("Xindy" "texindy %s" TeX-run-command nil t :help
> "Run xindy to create index file")
> ("Check" "lacheck %s" TeX-run-compile nil
> (latex-mode) :help "Check LaTeX file for correctness")
> ("ChkTeX" "chktex -v6 %s" TeX-run-compile nil
> (latex-mode) :help "Check LaTeX file for common mistakes")
> ("Spell" "(TeX-ispell-document \"\")"
> TeX-run-function nil t :help "Spell-check the document")
> ("Clean" "TeX-clean" TeX-run-function nil t :help
> "Delete generated intermediate files")
> ("Clean All" "(TeX-clean t)" TeX-run-function nil
> t :help "Delete generated intermediate and output files")
> ("Other" "" TeX-run-command t t :help "Run an
> arbitrary command"))
> )
>
> Content of the process buffer (displayed by C-c C-l):
>
> Running `LaTeX' on `aa' with ``pdflatex -file-line-error
> -interaction=nonstopmode "\input" "aa.tex"''
> This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/W32TeX)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> LaTeX2e <2017-04-15>
> Babel <3.18> and hyphenation patterns for 84 language(s) loaded.
> ! I can't find file `aa.tex'.
> <*> \input aa.tex
>
> (Press Enter to retry, or Control-Z to exit)
> Please type another input file name
> ! Emergency stop.
> <*> \input aa.tex
>
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on texput.log.
>
> TeX Output exited abnormally with code 1 at Sat Apr 7 09:20:05
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 14:41:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu,
In principle AUCTeX should just be giving the command you just gave, so there's something odd.
Can you try two more things:
1. Issue "C-c C-c Other", and at the prompt for the command type, literally (with an enter at the end):
pdflatex aa.tex
And see what happens.
2. Issue again "C-c C-c Other", and at the prompt for the command issue
pwd
and check the output with C-c C-l as usual. You should see something like
/cygdrive/d/
I'd just like to see what path is AUCTeX seeing and working in.
Cheers,
J
On 2018-04-07 16:17, Liyu Gong wrote:
> Hi Joe,
>
> I run pdflatex via windows command prompt, and produced a pdf file.
> The output message of the command is pasted below. My texlive was
> installed at C:\texlive. However, I just moved the aa.tex to C:\aa.tex
> then tried to compile it through AucTeX, the same error occurs again.
>
> Anyway, if nobody could reproduce the problem. I guess there must be
> something weird in my system. :)
>
> Best,
> Liyu
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 15:14:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu,
Sorry, I forgot to tell you about killing the first process.
> So I guess the problem is "pwd". My emacs is a windows version, not a
> cygwin version, so I should expect "d:/", but it says "/d".
Does it say "/d"? or "/d/", with a backlash at the end? Don't know if this is important, though.
I'm not sure what you mean by "windows version". My emacs is not run from a cygwin prompt, it's downloaded from
http://ftp.gnu.org/gnu/emacs/windows/
installed as-is, and run like other Windows programs. Where does yours come from?
If you can do one more experiment, you could try reinstalling the old auctex version that was working for you, and issue a "pwd" there as before, to see what kind of output it gives.
Cheers!
J
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 15:46:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu,
Very puzzling.
In the new auctex version (the one that's giving problems), can you issue a "C-c C-c Other" with this command:
pdflatex d:/aa.tex
and see whether it sees the file? It works for me.
Thank you for your patience.
J
On 2018-04-07 17:25, Liyu Gong wrote:
> Hi Joe,
>
> It said "/d", not "/d/"
>
> My emacs is download exactly the same address of yours. I mentioned
> cygwin because you said I should see something like "/cygdrive/d/"
> after pwd, and that's path is a cygwin path.
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 15:55:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 31079 <at> debbugs.gnu.org (full text, mbox):
gojjoe <at> gmail.com writes:
> Hi Liyu,
>
> Very puzzling.
>
> In the new auctex version (the one that's giving problems), can you
> issue a "C-c C-c Other" with this command:
>
> pdflatex d:/aa.tex
>
> and see whether it sees the file? It works for me.
How about
pdflatex "\input d:/aa.tex"
?
--
David Kastrup
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 16:08:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu and David,
It seems as if auctex is changing the working directory before calling pdflatex. But it doesn't do that with pwd.
Could this depend on the TEXINPUTS environment variable? Liyu, what is its value in your case? You can find it issuing "C-c C-c Other" with
echo %TEXINPUTS%
My value is
.;c:/Users/[omitted]/.emacs.d/elpa/auctex-12.1.1/latex;C:/Users/[omitted]/texmf/tex/;
Note the "." at the beginning, defaulting to the local directory.
Cheers,
J
On 2018-04-07 17:57, Liyu Gong wrote:
> Hi David,
>
> pdflatex "\input d:/aa.tex" got the same output as pdflatex d:/aa.tex
>
> Best,
> Liyu
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 16:24:01 GMT)
Full text and
rfc822 format available.
Message #32 received at 31079 <at> debbugs.gnu.org (full text, mbox):
PS:
> My value is
>
> .;c:/Users/[omitted]/.emacs.d/elpa/auctex-12.1.1/latex;C:/Users/[omitted]/texmf/tex/;
Curiously, only the last directory appears in my environment variable if I call it from a command prompt, outside Emacs. So the first two directories seem to be provided by AUCTeX itself.
I'm curious to see what its value is for you when called from Emacs in the way I described. You could also try the same with the old, working auctex version, to see if you get different results.
Cheers,
J
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 16:37:01 GMT)
Full text and
rfc822 format available.
Message #35 received at 31079 <at> debbugs.gnu.org (full text, mbox):
> Note that the path separator are different, for 12.1.1, it is ":", for
> 11.91.0, it is ";". I'm not sure whether it is important.
It surely is, given that ":" is to be intended as a normal character for a path (see the ":" right after "d").
But I have the same AUCTeX version as you, and it's inserting ";". I have Windows 7, though. I don't know the mechanism by which AUCTeX changes this environment variable... could it be that it's customized to the Windows version?
As far as I can see your init customization shouldn't trouble this environment variable, but I may be mistaken.
J
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 16:42:01 GMT)
Full text and
rfc822 format available.
Message #38 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Mmm... From the use of ":" as path separator, and the fact that "/cygwin/" is omitted, it almost looks like AUCTeX is seeing your machine as a Linux one...
If you issue "C-h v system-configuration", what value do you get?
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 16:49:02 GMT)
Full text and
rfc822 format available.
Message #41 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Sorry for these multiple replies.
Besides Emacs, I also have Cygwin and Msys32 installed in my Windows system. And at the beginning of my Emacs init file I have this:
(setenv "PATH" (concat "C:\\msys32\\mingw32\\bin;C:\\cygwin\\bin;C:\\cygwin\\lib;" (getenv "PATH")))
(setq exec-path (append '("C:/cygwin/bin" "C:/cygwin/lib" "C:/msys32/mingw32/bin") exec-path))
I wonder whether AUCTeX in my case is using some command from cygwin to update TEXINPUTS, and that takes care of the ";".
Do you also have cygwin on your system?
But I think that by now David has already guessed where the problem is, so I'll see what he says.
J
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 17:34:01 GMT)
Full text and
rfc822 format available.
Message #44 received at 31079 <at> debbugs.gnu.org (full text, mbox):
gojjoe <at> gmail.com writes:
> Sorry for these multiple replies.
>
> Besides Emacs, I also have Cygwin and Msys32 installed in my Windows
> system. And at the beginning of my Emacs init file I have this:
>
> (setenv "PATH" (concat
> "C:\\msys32\\mingw32\\bin;C:\\cygwin\\bin;C:\\cygwin\\lib;" (getenv
> "PATH")))
> (setq exec-path (append '("C:/cygwin/bin" "C:/cygwin/lib"
> "C:/msys32/mingw32/bin") exec-path))
>
> I wonder whether AUCTeX in my case is using some command from cygwin
> to update TEXINPUTS, and that takes care of the ";".
>
> Do you also have cygwin on your system?
>
> But I think that by now David has already guessed where the problem
> is, so I'll see what he says.
No, I haven't. But I suspect that in previous AUCTeX versions the path
separator was autodetected by explicitly calling kpse executables (which
is what I coded) and it has been replaced by some other code.
We had some iterations of that already if I remember correctly. The
problem addressed by the original code was that even on Windows, various
search path separators are in use depending on the TeX system in use and
its runtime environment, and they may even differ between command line
and configuration file.
--
David Kastrup
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 17:36:01 GMT)
Full text and
rfc822 format available.
Message #47 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi guys,
Thank you very much for looking into it. My system environment is as follows
aa.tex is at D:/aa.tex
OS: Windows 10 Home
Emacs: GNU Emacs 25.3.1 (x86_64-w64-mingw32) of 2017-09-26, which is
downloaded from the official gnu ftp site
TeX distribution: texlive-2017
Output of M-x TeX-submit-bug-report:
Emacs : GNU Emacs 25.3.1 (x86_64-w64-mingw32)
of 2017-09-26
Package: 12.1.1
current state:
==============
(setq
AUCTeX-date "2018-03-20"
window-system 'w32
LaTeX-version "2e"
TeX-style-path '("~/.emacs.d/auctex"
"d:/.emacs.d/elpa/auctex-12.1.1/style" "d:/.emacs.d/auctex/auto"
"d:/.emacs.d/auctex/style" "auto" "style")
TeX-auto-save t
TeX-parse-self t
TeX-master nil
TeX-command-list '(("TeX" "%(PDF)%(tex) %(file-line-error)
%(extraopts) %`%S%(PDFout)%(mode)%' %t" TeX-run-TeX nil
(plain-tex-mode ams-tex-mode texinfo-mode) :help
"Run plain TeX")
("LaTeX" "%`%l%(mode)%' %t" TeX-run-TeX nil
(latex-mode doctex-mode) :help "Run LaTeX")
("Makeinfo" "makeinfo %(extraopts) %t"
TeX-run-compile nil (texinfo-mode) :help "Run Makeinfo with Info
output")
("Makeinfo HTML" "makeinfo %(extraopts) --html %t"
TeX-run-compile nil (texinfo-mode) :help "Run Makeinfo with HTML
output")
("AmSTeX" "amstex %(PDFout) %(extraopts)
%`%S%(mode)%' %t" TeX-run-TeX nil (ams-tex-mode) :help "Run AMSTeX")
("ConTeXt" "%(cntxcom) --once --texutil
%(extraopts) %(execopts)%t" TeX-run-TeX nil (context-mode) :help "Run
ConTeXt once")
("ConTeXt Full" "%(cntxcom) %(extraopts)
%(execopts)%t" TeX-run-TeX nil (context-mode) :help "Run ConTeXt until
completion")
("BibTeX" "bibtex %s" TeX-run-BibTeX nil t :help
"Run BibTeX") ("Biber" "biber %s" TeX-run-Biber nil t :help "Run
Biber")
("View" "%V" TeX-run-discard-or-function t t :help
"Run Viewer") ("Print" "%p" TeX-run-command t t :help "Print the
file")
("Queue" "%q" TeX-run-background nil t :help "View
the printer queue" :visible TeX-queue-command)
("File" "%(o?)dvips %d -o %f " TeX-run-dvips t t
:help "Generate PostScript file")
("Dvips" "%(o?)dvips %d -o %f " TeX-run-dvips nil
t :help "Convert DVI file to PostScript")
("Dvipdfmx" "dvipdfmx %d" TeX-run-dvipdfmx nil t
:help "Convert DVI file to PDF with dvipdfmx")
("Ps2pdf" "ps2pdf %f" TeX-run-ps2pdf nil t :help
"Convert PostScript file to PDF")
("Glossaries" "makeglossaries %s" TeX-run-command
nil t :help "Run makeglossaries to create glossary file")
("Index" "makeindex %s" TeX-run-index nil t :help
"Run makeindex to create index file")
("upMendex" "upmendex %s" TeX-run-index t t :help
"Run upmendex to create index file")
("Xindy" "texindy %s" TeX-run-command nil t :help
"Run xindy to create index file")
("Check" "lacheck %s" TeX-run-compile nil
(latex-mode) :help "Check LaTeX file for correctness")
("ChkTeX" "chktex -v6 %s" TeX-run-compile nil
(latex-mode) :help "Check LaTeX file for common mistakes")
("Spell" "(TeX-ispell-document \"\")"
TeX-run-function nil t :help "Spell-check the document")
("Clean" "TeX-clean" TeX-run-function nil t :help
"Delete generated intermediate files")
("Clean All" "(TeX-clean t)" TeX-run-function nil
t :help "Delete generated intermediate and output files")
("Other" "" TeX-run-command t t :help "Run an
arbitrary command"))
)
Content of the process buffer (displayed by C-c C-l):
Running `LaTeX' on `aa' with ``pdflatex -file-line-error
-interaction=nonstopmode "\input" "aa.tex"''
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/W32TeX)
(preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
LaTeX2e <2017-04-15>
Babel <3.18> and hyphenation patterns for 84 language(s) loaded.
! I can't find file `aa.tex'.
<*> \input aa.tex
(Press Enter to retry, or Control-Z to exit)
Please type another input file name
! Emergency stop.
<*> \input aa.tex
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on texput.log.
TeX Output exited abnormally with code 1 at Sat Apr 7 09:20:05
Thanks!
Liyu
On Sat, Apr 7, 2018 at 6:52 AM, <gojjoe <at> gmail.com> wrote:
> Hi Liyu and Ikumi,
>
> Here: Windows 7 32-bit, Emacs 25.3.1, and AUCTeX 12.1.1 from elpa, and the file compiles smoothly for me too. I have no clue where the problem could be. Maybe problems with quotes and spaces in the path name, combined with a customized tex command? Liyu, it'd be useful if you shared the additional debugging info that Ikumi suggested
>
>> Additional information might be helpful, e.g.
>> - The output of M-x TeX-submit-bug-report
>> - The content of the process buffer (displayed by C-c C-l)
>> - The path name of directory where aa.tex is saved
>> - The type and year of your TeX distribution
>> - Whatever you think might be clue to resolve this issue
>
> Cheers,
> J
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 17:36:02 GMT)
Full text and
rfc822 format available.
Message #50 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Joe,
I run pdflatex via windows command prompt, and produced a pdf file.
The output message of the command is pasted below. My texlive was
installed at C:\texlive. However, I just moved the aa.tex to C:\aa.tex
then tried to compile it through AucTeX, the same error occurs again.
Anyway, if nobody could reproduce the problem. I guess there must be
something weird in my system. :)
Best,
Liyu
D:\>pdflatex aa.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/W32TeX)
(preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./aa.tex
LaTeX2e <2017-04-15>
Babel <3.18> and hyphenation patterns for 84 language(s) loaded.
(c:/texlive/2017/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(c:/texlive/2017/texmf-dist/tex/latex/base/size12.clo))
(c:/texlive/2017/texmf-dist/tex/latex/tree-dvips/lingmacros.sty)
(c:/texlive/2017/texmf-dist/tex/latex/tree-dvips/tree-dvips.sty
tree-dvips version .91 of May 16, 1995
)
No file aa.aux.
[1
Non-PDF special ignored!{c:/texlive/2017/texmf-var/fonts/map/pdftex/updmap/pdft
ex.map}
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!] (./aa.aux) )<c:/texlive/2017/texmf-dist/fonts/type1/p
ublic/amsfonts/cm/cmbx10.pfb><c:/texlive/2017/texmf-dist/fonts/type1/public/ams
fonts/cm/cmbx12.pfb><c:/texlive/2017/texmf-dist/fonts/type1/public/amsfonts/cm/
cmcsc10.pfb><c:/texlive/2017/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pf
b><c:/texlive/2017/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb><c:/texl
ive/2017/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb><c:/texlive/2017/t
exmf-dist/fonts/type1/public/amsfonts/cm/cmsy8.pfb><c:/texlive/2017/texmf-dist/
fonts/type1/public/amsfonts/cm/cmti12.pfb>
Output written on aa.pdf (1 page, 84758 bytes).
Transcript written on aa.log.
On Sat, Apr 7, 2018 at 9:57 AM, <gojjoe <at> gmail.com> wrote:
> Hi Liyu,
>
> The command call is just as mine, but I don't get any problem. It seems the problem is with tex-live rather than auctex.
>
> If you open a command prompt at D:\ and run the simple command
>
> pdflatex aa.tex
>
> then does the problem persist?
>
> Is your tex-live installed in the same partition (D:) as your tex file?
>
> Cheers,
> J
>
>
> On 2018-04-07 15:30, Liyu Gong wrote:
>> Hi guys,
>>
>> Thank you very much for looking into it. My system environment is as follows
>>
>> aa.tex is at D:/aa.tex
>>
>> OS: Windows 10 Home
>>
>> Emacs: GNU Emacs 25.3.1 (x86_64-w64-mingw32) of 2017-09-26, which is
>> downloaded from the official gnu ftp site
>>
>> TeX distribution: texlive-2017
>>
>> Output of M-x TeX-submit-bug-report:
>>
>> Emacs : GNU Emacs 25.3.1 (x86_64-w64-mingw32)
>> of 2017-09-26
>> Package: 12.1.1
>>
>> current state:
>> ==============
>> (setq
>> AUCTeX-date "2018-03-20"
>> window-system 'w32
>> LaTeX-version "2e"
>> TeX-style-path '("~/.emacs.d/auctex"
>> "d:/.emacs.d/elpa/auctex-12.1.1/style" "d:/.emacs.d/auctex/auto"
>> "d:/.emacs.d/auctex/style" "auto" "style")
>> TeX-auto-save t
>> TeX-parse-self t
>> TeX-master nil
>> TeX-command-list '(("TeX" "%(PDF)%(tex) %(file-line-error)
>> %(extraopts) %`%S%(PDFout)%(mode)%' %t" TeX-run-TeX nil
>> (plain-tex-mode ams-tex-mode texinfo-mode) :help
>> "Run plain TeX")
>> ("LaTeX" "%`%l%(mode)%' %t" TeX-run-TeX nil
>> (latex-mode doctex-mode) :help "Run LaTeX")
>> ("Makeinfo" "makeinfo %(extraopts) %t"
>> TeX-run-compile nil (texinfo-mode) :help "Run Makeinfo with Info
>> output")
>> ("Makeinfo HTML" "makeinfo %(extraopts) --html %t"
>> TeX-run-compile nil (texinfo-mode) :help "Run Makeinfo with HTML
>> output")
>> ("AmSTeX" "amstex %(PDFout) %(extraopts)
>> %`%S%(mode)%' %t" TeX-run-TeX nil (ams-tex-mode) :help "Run AMSTeX")
>> ("ConTeXt" "%(cntxcom) --once --texutil
>> %(extraopts) %(execopts)%t" TeX-run-TeX nil (context-mode) :help "Run
>> ConTeXt once")
>> ("ConTeXt Full" "%(cntxcom) %(extraopts)
>> %(execopts)%t" TeX-run-TeX nil (context-mode) :help "Run ConTeXt until
>> completion")
>> ("BibTeX" "bibtex %s" TeX-run-BibTeX nil t :help
>> "Run BibTeX") ("Biber" "biber %s" TeX-run-Biber nil t :help "Run
>> Biber")
>> ("View" "%V" TeX-run-discard-or-function t t :help
>> "Run Viewer") ("Print" "%p" TeX-run-command t t :help "Print the
>> file")
>> ("Queue" "%q" TeX-run-background nil t :help "View
>> the printer queue" :visible TeX-queue-command)
>> ("File" "%(o?)dvips %d -o %f " TeX-run-dvips t t
>> :help "Generate PostScript file")
>> ("Dvips" "%(o?)dvips %d -o %f " TeX-run-dvips nil
>> t :help "Convert DVI file to PostScript")
>> ("Dvipdfmx" "dvipdfmx %d" TeX-run-dvipdfmx nil t
>> :help "Convert DVI file to PDF with dvipdfmx")
>> ("Ps2pdf" "ps2pdf %f" TeX-run-ps2pdf nil t :help
>> "Convert PostScript file to PDF")
>> ("Glossaries" "makeglossaries %s" TeX-run-command
>> nil t :help "Run makeglossaries to create glossary file")
>> ("Index" "makeindex %s" TeX-run-index nil t :help
>> "Run makeindex to create index file")
>> ("upMendex" "upmendex %s" TeX-run-index t t :help
>> "Run upmendex to create index file")
>> ("Xindy" "texindy %s" TeX-run-command nil t :help
>> "Run xindy to create index file")
>> ("Check" "lacheck %s" TeX-run-compile nil
>> (latex-mode) :help "Check LaTeX file for correctness")
>> ("ChkTeX" "chktex -v6 %s" TeX-run-compile nil
>> (latex-mode) :help "Check LaTeX file for common mistakes")
>> ("Spell" "(TeX-ispell-document \"\")"
>> TeX-run-function nil t :help "Spell-check the document")
>> ("Clean" "TeX-clean" TeX-run-function nil t :help
>> "Delete generated intermediate files")
>> ("Clean All" "(TeX-clean t)" TeX-run-function nil
>> t :help "Delete generated intermediate and output files")
>> ("Other" "" TeX-run-command t t :help "Run an
>> arbitrary command"))
>> )
>>
>> Content of the process buffer (displayed by C-c C-l):
>>
>> Running `LaTeX' on `aa' with ``pdflatex -file-line-error
>> -interaction=nonstopmode "\input" "aa.tex"''
>> This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/W32TeX)
>> (preloaded format=pdflatex)
>> restricted \write18 enabled.
>> entering extended mode
>> LaTeX2e <2017-04-15>
>> Babel <3.18> and hyphenation patterns for 84 language(s) loaded.
>> ! I can't find file `aa.tex'.
>> <*> \input aa.tex
>>
>> (Press Enter to retry, or Control-Z to exit)
>> Please type another input file name
>> ! Emergency stop.
>> <*> \input aa.tex
>>
>> ! ==> Fatal error occurred, no output PDF file produced!
>> Transcript written on texput.log.
>>
>> TeX Output exited abnormally with code 1 at Sat Apr 7 09:20:05
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 17:36:02 GMT)
Full text and
rfc822 format available.
Message #53 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Joe,
After I run "C-c C-c Other", the output of "C-c C-l" is:
Running `Other' on `aa' with ``pdflatex aa.tex''
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/W32TeX)
(preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
! I can't find file `aa.tex'.
<*> aa.tex
(Press Enter to retry, or Control-Z to exit)
Please type another input file name:
Then I kill the "C-c C-l" buffer because it is still running and
waiting for input which I can not type.
Then I run "C-c C-c Other" with "pwd", the output of "C-c C-l" says:
Running `Other' on `aa' with ``pwd''
/d
TeX Output finished at Sat Apr 7 10:51:22
So I guess the problem is "pwd". My emacs is a windows version, not a
cygwin version, so I should expect "d:/", but it says "/d".
Best,
Liyu
On Sat, Apr 7, 2018 at 10:40 AM, <gojjoe <at> gmail.com> wrote:
> Hi Liyu,
>
> In principle AUCTeX should just be giving the command you just gave, so there's something odd.
>
> Can you try two more things:
>
> 1. Issue "C-c C-c Other", and at the prompt for the command type, literally (with an enter at the end):
>
> pdflatex aa.tex
>
> And see what happens.
>
> 2. Issue again "C-c C-c Other", and at the prompt for the command issue
>
> pwd
>
> and check the output with C-c C-l as usual. You should see something like
>
> /cygdrive/d/
>
> I'd just like to see what path is AUCTeX seeing and working in.
>
> Cheers,
> J
>
>
> On 2018-04-07 16:17, Liyu Gong wrote:
>> Hi Joe,
>>
>> I run pdflatex via windows command prompt, and produced a pdf file.
>> The output message of the command is pasted below. My texlive was
>> installed at C:\texlive. However, I just moved the aa.tex to C:\aa.tex
>> then tried to compile it through AucTeX, the same error occurs again.
>>
>> Anyway, if nobody could reproduce the problem. I guess there must be
>> something weird in my system. :)
>>
>> Best,
>> Liyu
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 17:36:03 GMT)
Full text and
rfc822 format available.
Message #56 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Joe,
It said "/d", not "/d/"
My emacs is download exactly the same address of yours. I mentioned
cygwin because you said I should see something like "/cygdrive/d/"
after pwd, and that's path is a cygwin path.
I just tried the old version (11.91.0). The output of "C-c C-c Other"
with pdflatex is:
Running `Other' on `aa' with ``pdflatex aa.tex''
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/W32TeX)
(preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./aa.tex
LaTeX2e <2017-04-15>
Babel <3.18> and hyphenation patterns for 84 language(s) loaded.
(c:/texlive/2017/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(c:/texlive/2017/texmf-dist/tex/latex/base/size12.clo))
(c:/texlive/2017/texmf-dist/tex/latex/tree-dvips/lingmacros.sty)
(c:/texlive/2017/texmf-dist/tex/latex/tree-dvips/tree-dvips.sty
tree-dvips version .91 of May 16, 1995
)
No file aa.aux.
[1
Non-PDF special ignored!{c:/texlive/2017/texmf-var/fonts/map/pdftex/updmap/pdft
ex.map}
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!
Non-PDF special ignored!] (./aa.aux) )<c:/texlive/2017/texmf-dist/fonts/type1/p
ublic/amsfonts/cm/cmbx10.pfb><c:/texlive/2017/texmf-dist/fonts/type1/public/ams
fonts/cm/cmbx12.pfb><c:/texlive/2017/texmf-dist/fonts/type1/public/amsfonts/cm/
cmcsc10.pfb><c:/texlive/2017/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pf
b><c:/texlive/2017/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb><c:/texl
ive/2017/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb><c:/texlive/2017/t
exmf-dist/fonts/type1/public/amsfonts/cm/cmsy8.pfb><c:/texlive/2017/texmf-dist/
fonts/type1/public/amsfonts/cm/cmti12.pfb>
Output written on aa.pdf (1 page, 84758 bytes).
Transcript written on aa.log.
TeX Output finished at Sat Apr 7 11:18:43
and the output of "C-c C-c Other" with "pwd" is:
Running `Other' on `aa' with ``pwd''
/d
TeX Output finished at Sat Apr 7 11:21:38
It seems the output of "pwd" is the same as the newest version.
Thanks,
Liyu
On Sat, Apr 7, 2018 at 11:13 AM, <gojjoe <at> gmail.com> wrote:
> Hi Liyu,
>
> Sorry, I forgot to tell you about killing the first process.
>
>> So I guess the problem is "pwd". My emacs is a windows version, not a
>> cygwin version, so I should expect "d:/", but it says "/d".
>
> Does it say "/d"? or "/d/", with a backlash at the end? Don't know if this is important, though.
>
> I'm not sure what you mean by "windows version". My emacs is not run from a cygwin prompt, it's downloaded from
>
> http://ftp.gnu.org/gnu/emacs/windows/
>
> installed as-is, and run like other Windows programs. Where does yours come from?
>
> If you can do one more experiment, you could try reinstalling the old auctex version that was working for you, and issue a "pwd" there as before, to see what kind of output it gives.
>
> Cheers!
> J
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 17:36:03 GMT)
Full text and
rfc822 format available.
Message #59 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Joe,
I tried "C-c C-c Other" with pdflatex d:/aa.tex. Now it can see
"aa.tex", but can not find "article.cls". The output is:
Running `Other' on `aa' with ``pdflatex d:/aa.tex''
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/W32TeX)
(preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(d:/aa.tex
LaTeX2e <2017-04-15>
Babel <3.18> and hyphenation patterns for 84 language(s) loaded.
! LaTeX Error: File `article.cls' not found.
Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: cls)
Enter file name:
Thanks for debugging.
Best,
Liyu
On Sat, Apr 7, 2018 at 11:45 AM, <gojjoe <at> gmail.com> wrote:
> Hi Liyu,
>
> Very puzzling.
>
> In the new auctex version (the one that's giving problems), can you issue a "C-c C-c Other" with this command:
>
> pdflatex d:/aa.tex
>
> and see whether it sees the file? It works for me.
>
> Thank you for your patience.
> J
>
> On 2018-04-07 17:25, Liyu Gong wrote:
>> Hi Joe,
>>
>> It said "/d", not "/d/"
>>
>> My emacs is download exactly the same address of yours. I mentioned
>> cygwin because you said I should see something like "/cygdrive/d/"
>> after pwd, and that's path is a cygwin path.
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 17:36:04 GMT)
Full text and
rfc822 format available.
Message #62 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi David,
pdflatex "\input d:/aa.tex" got the same output as pdflatex d:/aa.tex
Best,
Liyu
On Sat, Apr 7, 2018 at 11:54 AM, David Kastrup <dak <at> gnu.org> wrote:
> gojjoe <at> gmail.com writes:
>
>> Hi Liyu,
>>
>> Very puzzling.
>>
>> In the new auctex version (the one that's giving problems), can you
>> issue a "C-c C-c Other" with this command:
>>
>> pdflatex d:/aa.tex
>>
>> and see whether it sees the file? It works for me.
>
> How about
>
> pdflatex "\input d:/aa.tex"
>
> ?
>
> --
> David Kastrup
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 17:36:04 GMT)
Full text and
rfc822 format available.
Message #65 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Joe and David,
My values is:
.:d:/.emacs.d/elpa/auctex-12.1.1/latex:
on the old version which works for the file, the value is:
.;d:/.emacs.d/elpa/auctex-11.91.0/latex;
Note that the path separator are different, for 12.1.1, it is ":", for
11.91.0, it is ";". I'm not sure whether it is important.
By the way, my AucTeX setting up script is:
(setq TeX-auto-save t)
(setq TeX-parse-self t)
(setq-default TeX-master nil)
(setq TeX-PDF-mode t)
(add-hook 'LaTeX-mode-hook 'turn-on-reftex)
(setq reftex-plug-into-AUCTeX t)
(add-hook 'LaTeX-mode-hook (lambda() (TeX-fold-mode 1)))
Thanks,
Liyu
On Sat, Apr 7, 2018 at 12:06 PM, <gojjoe <at> gmail.com> wrote:
> Hi Liyu and David,
>
> It seems as if auctex is changing the working directory before calling pdflatex. But it doesn't do that with pwd.
>
> Could this depend on the TEXINPUTS environment variable? Liyu, what is its value in your case? You can find it issuing "C-c C-c Other" with
>
> echo %TEXINPUTS%
>
> My value is
>
> .;c:/Users/[omitted]/.emacs.d/elpa/auctex-12.1.1/latex;C:/Users/[omitted]/texmf/tex/;
>
> Note the "." at the beginning, defaulting to the local directory.
>
> Cheers,
> J
>
> On 2018-04-07 17:57, Liyu Gong wrote:
>> Hi David,
>>
>> pdflatex "\input d:/aa.tex" got the same output as pdflatex d:/aa.tex
>>
>> Best,
>> Liyu
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 17:36:05 GMT)
Full text and
rfc822 format available.
Message #68 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Joe,
The values I pasted in my previous email was produced by calling the
command from Emacs with "C-c C-c Other". I'm not sure how to call it
outside Emacs, but there is no environment variable TEXINPUTS in my
windows system, and the directories does not exist in my PATH either.
Best,
Liyu
On Sat, Apr 7, 2018 at 12:23 PM, <gojjoe <at> gmail.com> wrote:
> PS:
>
>> My value is
>>
>> .;c:/Users/[omitted]/.emacs.d/elpa/auctex-12.1.1/latex;C:/Users/[omitted]/texmf/tex/;
>
> Curiously, only the last directory appears in my environment variable if I call it from a command prompt, outside Emacs. So the first two directories seem to be provided by AUCTeX itself.
>
> I'm curious to see what its value is for you when called from Emacs in the way I described. You could also try the same with the old, working auctex version, to see if you get different results.
>
> Cheers,
> J
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 17:36:05 GMT)
Full text and
rfc822 format available.
Message #71 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi,
My value for system-configuration is: "x86_64-w64-mingw32"
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))
But the TEXINPUTS is the same.
Did you installed some Emacs package like cygwin-mount. I remember
there are such kind of packages which can let NTEmacs using cygwin
programs, but I didn't installed them.
Thanks,
Liyu
On Sat, Apr 7, 2018 at 12:48 PM, <gojjoe <at> gmail.com> wrote:
> Sorry for these multiple replies.
>
> Besides Emacs, I also have Cygwin and Msys32 installed in my Windows system. And at the beginning of my Emacs init file I have this:
>
> (setenv "PATH" (concat "C:\\msys32\\mingw32\\bin;C:\\cygwin\\bin;C:\\cygwin\\lib;" (getenv "PATH")))
> (setq exec-path (append '("C:/cygwin/bin" "C:/cygwin/lib" "C:/msys32/mingw32/bin") exec-path))
>
> I wonder whether AUCTeX in my case is using some command from cygwin to update TEXINPUTS, and that takes care of the ";".
>
> Do you also have cygwin on your system?
>
> But I think that by now David has already guessed where the problem is, so I'll see what he says.
>
> J
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 17:57:02 GMT)
Full text and
rfc822 format available.
Message #74 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Liyu Gong <liyu.gong <at> uky.edu> writes:
> Hi Joe and David,
>
> My values is:
> .:d:/.emacs.d/elpa/auctex-12.1.1/latex:
>
> on the old version which works for the file, the value is:
> .;d:/.emacs.d/elpa/auctex-11.91.0/latex;
>
> Note that the path separator are different, for 12.1.1, it is ":", for
> 11.91.0, it is ";". I'm not sure whether it is important.
It likely is.
--
David Kastrup
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 19:03:02 GMT)
Full text and
rfc822 format available.
Message #77 received at 31079 <at> debbugs.gnu.org (full text, mbox):
I was thinking about possible fixes, even dirty ones, like adding "-output-directory=./" to pdflatex via customize; and similar ones. But it's likely that pdflatex will still not see the files of the tex distribution, like cls files etc.
Anyway, if you want to give this a try, do this:
Issue "M-x customize-apropos" and give "tex-command-list" as an expression (without quotes). Then the full TeX-command-list should appear, and you should find two lines that read somewhat like this:
Name: LaTeX
Command: %`%l%(mode)%' %t
Now modify the argument of Command:, that is, "%`%l%(mode)%' %t" to this:
pdflatex -interaction=nonstopmode -output-directory=./ \"\\input\" %t
And then save this variable (at the bottom of the full list) for all future sessions. Let me know if this trick works.
I've also tried to issue something like
(start-process "setting TEXINPUTS" nil "set" "TEXINPUTS=.;")
after LaTeX-mode is loaded, but it doesn't seem to change the TEXINPUTS variable in any way...
Cheers,
J
On 2018-04-07 19:56, David Kastrup wrote:
> Liyu Gong <liyu.gong <at> uky.edu> writes:
>
>> Hi Joe and David,
>>
>> My values is:
>> .:d:/.emacs.d/elpa/auctex-12.1.1/latex:
>>
>> on the old version which works for the file, the value is:
>> .;d:/.emacs.d/elpa/auctex-11.91.0/latex;
>>
>> Note that the path separator are different, for 12.1.1, it is ":", for
>> 11.91.0, it is ";". I'm not sure whether it is important.
>
> It likely is.
>
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 19:44:02 GMT)
Full text and
rfc822 format available.
Message #80 received at 31079 <at> debbugs.gnu.org (full text, mbox):
> I tried the trick to replace the command, but it produce the following error:
Sorry, there was no need to escape characters like I did. Try this instead:
pdflatex -interaction=nonstopmode -output-directory=./ "\input" %t
Fingers crossed...
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sat, 07 Apr 2018 19:49:02 GMT)
Full text and
rfc822 format available.
Message #83 received at 31079 <at> debbugs.gnu.org (full text, mbox):
This time, the file "article.cls" can't be found ....
Running `LaTeX' on `aa' with ``pdflatex -interaction=nonstopmode
-output-directory=./ "\input" "aa.tex"''
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/W32TeX)
(preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
LaTeX2e <2017-04-15>
Babel <3.18> and hyphenation patterns for 84 language(s) loaded.
(.//aa.tex
! LaTeX Error: File `article.cls' not found.
Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: cls)
Enter file name:
! Emergency stop.
<read *>
l.2 \usepackage
{lingmacros}^^M
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on .//aa.log.
TeX Output exited abnormally with code 1 at Sat Apr 7 15:46:27
Best,
Liyu
On Sat, Apr 7, 2018 at 3:42 PM, <gojjoe <at> gmail.com> wrote:
>
>> I tried the trick to replace the command, but it produce the following error:
>
> Sorry, there was no need to escape characters like I did. Try this instead:
>
> pdflatex -interaction=nonstopmode -output-directory=./ "\input" %t
>
>
> Fingers crossed...
>
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 04:02:02 GMT)
Full text and
rfc822 format available.
Message #86 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu, thanks for your cooperation.
>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
> Hi Joe and David,
> My values is:
> .:d:/.emacs.d/elpa/auctex-12.1.1/latex:
> on the old version which works for the file, the value is:
> .;d:/.emacs.d/elpa/auctex-11.91.0/latex;
> Note that the path separator are different, for 12.1.1, it is ":", for
> 11.91.0, it is ";". I'm not sure whether it is important.
Apparently the change I introduced in
https://lists.gnu.org/archive/html/auctex-devel/2017-12/msg00016.html
interferes with `preview-TeX-style-cooked' and it does not use the right
separator.
I'll look into that from now on.
Could you provide the value of the elisp variable
`TeX-kpathsea-path-delimiter' ?
Regards,
Ikumi Keita
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 04:10:02 GMT)
Full text and
rfc822 format available.
Message #89 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Ikumi,
The value is ":"
TeX-kpathsea-path-delimiter is a variable defined in ‘tex.el’.
Its value is ":"
Documentation:
Path delimiter for kpathsea output.
t means autodetect, nil means kpathsea is disabled.
You can customize this variable.
Thanks,
Liyu
On Sun, Apr 8, 2018 at 12:00 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
> Hi Liyu, thanks for your cooperation.
>
>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>> Hi Joe and David,
>> My values is:
>> .:d:/.emacs.d/elpa/auctex-12.1.1/latex:
>
>> on the old version which works for the file, the value is:
>> .;d:/.emacs.d/elpa/auctex-11.91.0/latex;
>
>> Note that the path separator are different, for 12.1.1, it is ":", for
>> 11.91.0, it is ";". I'm not sure whether it is important.
>
> Apparently the change I introduced in
> https://lists.gnu.org/archive/html/auctex-devel/2017-12/msg00016.html
> interferes with `preview-TeX-style-cooked' and it does not use the right
> separator.
> I'll look into that from now on.
>
> Could you provide the value of the elisp variable
> `TeX-kpathsea-path-delimiter' ?
>
> Regards,
> Ikumi Keita
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 04:16:01 GMT)
Full text and
rfc822 format available.
Message #92 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Ahha,
This is it. I customized the variable TeX-kpathsea-path-delimiter to
";", then the aa.tex file can be compiled smoothly.
Thanks,
Liyu
On Sun, Apr 8, 2018 at 12:09 AM, Liyu Gong <liyu.gong <at> uky.edu> wrote:
> Hi Ikumi,
>
> The value is ":"
>
> TeX-kpathsea-path-delimiter is a variable defined in ‘tex.el’.
> Its value is ":"
>
> Documentation:
> Path delimiter for kpathsea output.
> t means autodetect, nil means kpathsea is disabled.
>
> You can customize this variable.
>
> Thanks,
> Liyu
>
> On Sun, Apr 8, 2018 at 12:00 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
>> Hi Liyu, thanks for your cooperation.
>>
>>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>>> Hi Joe and David,
>>> My values is:
>>> .:d:/.emacs.d/elpa/auctex-12.1.1/latex:
>>
>>> on the old version which works for the file, the value is:
>>> .;d:/.emacs.d/elpa/auctex-11.91.0/latex;
>>
>>> Note that the path separator are different, for 12.1.1, it is ":", for
>>> 11.91.0, it is ";". I'm not sure whether it is important.
>>
>> Apparently the change I introduced in
>> https://lists.gnu.org/archive/html/auctex-devel/2017-12/msg00016.html
>> interferes with `preview-TeX-style-cooked' and it does not use the right
>> separator.
>> I'll look into that from now on.
>>
>> Could you provide the value of the elisp variable
>> `TeX-kpathsea-path-delimiter' ?
>>
>> Regards,
>> Ikumi Keita
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 04:37:02 GMT)
Full text and
rfc822 format available.
Message #95 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu,
Thanks, very helpful. Then the auto detection of kpathsea path
delimiter returns wrong result on your environment.
I guess that you have two different TeX distribution, texlive for w32
and texlive for cygwin, and the latter is used for auto detection while
the former is used at actually running (pdf)latex.
Could you please tell me what string is inserted in the buffer when you
evaluate the following form in the *scratch* buffer?
(call-process "kpsewhich" nil
(list standard-output nil) nil
"--expand-path" "{.,..}")
Regards,
Ikumi Keita
>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
> Ahha,
> This is it. I customized the variable TeX-kpathsea-path-delimiter to
> ";", then the aa.tex file can be compiled smoothly.
> Thanks,
> Liyu
> On Sun, Apr 8, 2018 at 12:09 AM, Liyu Gong <liyu.gong <at> uky.edu> wrote:
>> Hi Ikumi,
>>
>> The value is ":"
>>
>> TeX-kpathsea-path-delimiter is a variable defined in ‘tex.el’.
>> Its value is ":"
>>
>> Documentation:
>> Path delimiter for kpathsea output.
>> t means autodetect, nil means kpathsea is disabled.
>>
>> You can customize this variable.
>>
>> Thanks,
>> Liyu
>>
>> On Sun, Apr 8, 2018 at 12:00 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
>>> Hi Liyu, thanks for your cooperation.
>>>
>>>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>>>> Hi Joe and David,
>>>> My values is:
>>>> .:d:/.emacs.d/elpa/auctex-12.1.1/latex:
>>>
>>>> on the old version which works for the file, the value is:
>>>> .;d:/.emacs.d/elpa/auctex-11.91.0/latex;
>>>
>>>> Note that the path separator are different, for 12.1.1, it is ":", for
>>>> 11.91.0, it is ";". I'm not sure whether it is important.
>>>
>>> Apparently the change I introduced in
>>> https://lists.gnu.org/archive/html/auctex-devel/2017-12/msg00016.html
>>> interferes with `preview-TeX-style-cooked' and it does not use the right
>>> separator.
>>> I'll look into that from now on.
>>>
>>> Could you provide the value of the elisp variable
>>> `TeX-kpathsea-path-delimiter' ?
>>>
>>> Regards,
>>> Ikumi Keita
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 04:50:02 GMT)
Full text and
rfc822 format available.
Message #98 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Ikumni,
The result of the evaluation is: 1 (#o1, #x1, ?\C-a)
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.
Thanks,
Liyu
On Sun, Apr 8, 2018 at 12:36 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
> Hi Liyu,
>
> Thanks, very helpful. Then the auto detection of kpathsea path
> delimiter returns wrong result on your environment.
>
> I guess that you have two different TeX distribution, texlive for w32
> and texlive for cygwin, and the latter is used for auto detection while
> the former is used at actually running (pdf)latex.
>
> Could you please tell me what string is inserted in the buffer when you
> evaluate the following form in the *scratch* buffer?
> (call-process "kpsewhich" nil
> (list standard-output nil) nil
> "--expand-path" "{.,..}")
>
> Regards,
> Ikumi Keita
>
>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>> Ahha,
>> This is it. I customized the variable TeX-kpathsea-path-delimiter to
>> ";", then the aa.tex file can be compiled smoothly.
>
>> Thanks,
>> Liyu
>
>> On Sun, Apr 8, 2018 at 12:09 AM, Liyu Gong <liyu.gong <at> uky.edu> wrote:
>>> Hi Ikumi,
>>>
>>> The value is ":"
>>>
>>> TeX-kpathsea-path-delimiter is a variable defined in ‘tex.el’.
>>> Its value is ":"
>>>
>>> Documentation:
>>> Path delimiter for kpathsea output.
>>> t means autodetect, nil means kpathsea is disabled.
>>>
>>> You can customize this variable.
>>>
>>> Thanks,
>>> Liyu
>>>
>>> On Sun, Apr 8, 2018 at 12:00 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
>>>> Hi Liyu, thanks for your cooperation.
>>>>
>>>>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>>>>> Hi Joe and David,
>>>>> My values is:
>>>>> .:d:/.emacs.d/elpa/auctex-12.1.1/latex:
>>>>
>>>>> on the old version which works for the file, the value is:
>>>>> .;d:/.emacs.d/elpa/auctex-11.91.0/latex;
>>>>
>>>>> Note that the path separator are different, for 12.1.1, it is ":", for
>>>>> 11.91.0, it is ";". I'm not sure whether it is important.
>>>>
>>>> Apparently the change I introduced in
>>>> https://lists.gnu.org/archive/html/auctex-devel/2017-12/msg00016.html
>>>> interferes with `preview-TeX-style-cooked' and it does not use the right
>>>> separator.
>>>> I'll look into that from now on.
>>>>
>>>> Could you provide the value of the elisp variable
>>>> `TeX-kpathsea-path-delimiter' ?
>>>>
>>>> Regards,
>>>> Ikumi Keita
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 05:00:02 GMT)
Full text and
rfc822 format available.
Message #101 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu, thanks for your patience.
>>>>> Liyu Gong <liyu.gong <at> 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
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 05:10:02 GMT)
Full text and
rfc822 format available.
Message #104 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Ikumi,
After evaluation, there is only a dot inserted right at where I type "C-x C-e".
.
Thanks,
Liyu
On Sun, Apr 8, 2018 at 12:59 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
> Hi Liyu, thanks for your patience.
>
>>>>>> Liyu Gong <liyu.gong <at> 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
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 05:13:02 GMT)
Full text and
rfc822 format available.
Message #107 received at 31079 <at> debbugs.gnu.org (full text, mbox):
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.gong <at> uky.edu> wrote:
> Hi Ikumi,
>
> After evaluation, there is only a dot inserted right at where I type "C-x C-e".
> .
>
> Thanks,
> Liyu
>
>
> On Sun, Apr 8, 2018 at 12:59 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
>> Hi Liyu, thanks for your patience.
>>
>>>>>>> Liyu Gong <liyu.gong <at> 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
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 05:23:02 GMT)
Full text and
rfc822 format available.
Message #110 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu,
>>>>> Liyu Gong <liyu.gong <at> 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.gong <at> 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 <ikumi <at> ikumi.que.jp> wrote:
>>> Hi Liyu, thanks for your patience.
>>>
>>>>>>>> Liyu Gong <liyu.gong <at> 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
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 06:07:02 GMT)
Full text and
rfc822 format available.
Message #113 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Ikumi Keita <ikumi <at> ikumi.que.jp> writes:
> Hi Liyu,
>
>>>>>> Liyu Gong <liyu.gong <at> 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.gong <at> 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.
Perhaps related to the security settings of TeXlive?
--
David Kastrup
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 06:09:01 GMT)
Full text and
rfc822 format available.
Message #116 received at 31079 <at> debbugs.gnu.org (full text, mbox):
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
delimiter.
Regards,
Ikumi Keita
>>>>> Ikumi Keita <ikumi <at> ikumi.que.jp> writes:
> Hi Liyu,
>>>>> Liyu Gong <liyu.gong <at> 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.gong <at> 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 <ikumi <at> ikumi.que.jp> wrote:
>>>> Hi Liyu, thanks for your patience.
>>>>
>>>>>>>>> Liyu Gong <liyu.gong <at> 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
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 06:36:02 GMT)
Full text and
rfc822 format available.
Message #119 received at 31079 <at> debbugs.gnu.org (full text, mbox):
>>>>> David Kastrup <dak <at> gnu.org> writes:
>> 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.
> Perhaps related to the security settings of TeXlive?
Possibly. But I cannot find out such description in the kpathsea info
file yet.
Regards,
Ikumi Keita
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 12:01:01 GMT)
Full text and
rfc822 format available.
Message #122 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Ikumi,
Sorry, I just got up. The results is the same: a dot followed with a
newline "\n"
Best,
Liyu
On Sun, Apr 8, 2018 at 2:08 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
> 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
> delimiter.
>
> Regards,
> Ikumi Keita
>
>>>>>> Ikumi Keita <ikumi <at> ikumi.que.jp> writes:
>> Hi Liyu,
>>>>>> Liyu Gong <liyu.gong <at> 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.gong <at> 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 <ikumi <at> ikumi.que.jp> wrote:
>>>>> Hi Liyu, thanks for your patience.
>>>>>
>>>>>>>>>> Liyu Gong <liyu.gong <at> 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
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 12:36:01 GMT)
Full text and
rfc822 format available.
Message #125 received at 31079 <at> debbugs.gnu.org (full text, mbox):
>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
> Hi Ikumi,
> Sorry, I just got up. The results is the same: a dot followed with a
> newline "\n"
Thanks. Well, then...
1. How about the following two?
(call-process "kpsewhich" nil (list standard-output nil) nil
"--expand-brace" "{.,..}")
(call-process "kpsewhich" nil (list standard-output nil) nil
"--expand-brace" "{.,./.}")
2. Could you issue the following command with windows command prompt?
kpsewhich --version
Best regards,
Ikumi Keita
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 13:16:01 GMT)
Full text and
rfc822 format available.
Message #128 received at 31079 <at> debbugs.gnu.org (full text, mbox):
On Sun, Apr 8, 2018 at 8:35 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>> Hi Ikumi,
>> Sorry, I just got up. The results is the same: a dot followed with a
>> newline "\n"
>
> Thanks. Well, then...
>
> 1. How about the following two?
>
> (call-process "kpsewhich" nil (list standard-output nil) nil
> "--expand-brace" "{.,..}")
>
> (call-process "kpsewhich" nil (list standard-output nil) nil
> "--expand-brace" "{.,./.}")
>
These two produce the same result: a dot followed by a newline "\n"
> 2. Could you issue the following command with windows command prompt?
> kpsewhich --version
C:\Users\gongl>kpsewhich --version
kpathsea version 6.2.3
Copyright 2017 Karl Berry & Olaf Weber.
License LGPLv2.1+: GNU Lesser GPL version 2.1 or later
<http://gnu.org/licenses/lgpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
>
> Best regards,
> Ikumi Keita
Best,
Liyu
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 13:38:02 GMT)
Full text and
rfc822 format available.
Message #131 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Liyu, thank you very much.
>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
> On Sun, Apr 8, 2018 at 8:35 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
>>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>>> Hi Ikumi,
>>> Sorry, I just got up. The results is the same: a dot followed with a
>>> newline "\n"
>>
>> Thanks. Well, then...
>>
>> 1. How about the following two?
>>
>> (call-process "kpsewhich" nil (list standard-output nil) nil
>> "--expand-brace" "{.,..}")
>>
>> (call-process "kpsewhich" nil (list standard-output nil) nil
>> "--expand-brace" "{.,./.}")
>>
> These two produce the same result: a dot followed by a newline "\n"
>> 2. Could you issue the following command with windows command prompt?
>> kpsewhich --version
> C:\Users\gongl>kpsewhich --version
> kpathsea version 6.2.3
> Copyright 2017 Karl Berry & Olaf Weber.
> License LGPLv2.1+: GNU Lesser GPL version 2.1 or later
> <http://gnu.org/licenses/lgpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
Then the kpsewhich binary must really be the official texlive version.
I'm a sort of giving up.
I suppose this can hardly be the case, `call-process' might not call the
same binary. What does (executable-find "kpsewhich") return? On my
w32 emacs 25.2, it returns "c:/texlive/2017/bin/win32/kpsewhich.exe".
Best,
Ikumi Keita
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 13:48:02 GMT)
Full text and
rfc822 format available.
Message #134 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Ikumi,
The results is: "c:/cygwin64/bin/kpsewhich.exe" !!!!!!!!!
Sorry, I must messed up somewhere in my system. Thank you so much!
Best,
Liyu
On Sun, Apr 8, 2018 at 9:37 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
> Liyu, thank you very much.
>
>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>> On Sun, Apr 8, 2018 at 8:35 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
>>>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>>>> Hi Ikumi,
>>>> Sorry, I just got up. The results is the same: a dot followed with a
>>>> newline "\n"
>>>
>>> Thanks. Well, then...
>>>
>>> 1. How about the following two?
>>>
>>> (call-process "kpsewhich" nil (list standard-output nil) nil
>>> "--expand-brace" "{.,..}")
>>>
>>> (call-process "kpsewhich" nil (list standard-output nil) nil
>>> "--expand-brace" "{.,./.}")
>>>
>
>> These two produce the same result: a dot followed by a newline "\n"
>
>>> 2. Could you issue the following command with windows command prompt?
>>> kpsewhich --version
>
>> C:\Users\gongl>kpsewhich --version
>> kpathsea version 6.2.3
>> Copyright 2017 Karl Berry & Olaf Weber.
>> License LGPLv2.1+: GNU Lesser GPL version 2.1 or later
>> <http://gnu.org/licenses/lgpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>
> Then the kpsewhich binary must really be the official texlive version.
> I'm a sort of giving up.
> I suppose this can hardly be the case, `call-process' might not call the
> same binary. What does (executable-find "kpsewhich") return? On my
> w32 emacs 25.2, it returns "c:/texlive/2017/bin/win32/kpsewhich.exe".
>
> Best,
> Ikumi Keita
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 13:48:02 GMT)
Full text and
rfc822 format available.
Message #137 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Ikumi Keita <ikumi <at> ikumi.que.jp> writes:
> Liyu, thank you very much.
>
>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>> On Sun, Apr 8, 2018 at 8:35 AM, Ikumi Keita <ikumi <at> ikumi.que.jp> wrote:
>>>>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
>>>> Hi Ikumi,
>>>> Sorry, I just got up. The results is the same: a dot followed with a
>>>> newline "\n"
>>>
>>> Thanks. Well, then...
>>>
>>> 1. How about the following two?
>>>
>>> (call-process "kpsewhich" nil (list standard-output nil) nil
>>> "--expand-brace" "{.,..}")
>>>
>>> (call-process "kpsewhich" nil (list standard-output nil) nil
>>> "--expand-brace" "{.,./.}")
>>>
>
>> These two produce the same result: a dot followed by a newline "\n"
>
>>> 2. Could you issue the following command with windows command prompt?
>>> kpsewhich --version
>
>> C:\Users\gongl>kpsewhich --version
>> kpathsea version 6.2.3
>> Copyright 2017 Karl Berry & Olaf Weber.
>> License LGPLv2.1+: GNU Lesser GPL version 2.1 or later
>> <http://gnu.org/licenses/lgpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>
> Then the kpsewhich binary must really be the official texlive version.
> I'm a sort of giving up.
Again: I suppose that may be an artifact of security settings, like one
of the following options in texmf.cnf:
% This is used by the Windows script wrapper for restricting searching
% for the purportedly safe shell_escape_commands above to system
% directories.
TEXMF_RESTRICTED_SCRIPTS = \
{!!$TEXMFLOCAL,!!$TEXMFDIST}/scripts/{$progname,$engine,}//
% Do we allow TeX \input or \openin (openin_any), or \openout
% (openout_any) on filenames starting with `.' (e.g., .rhosts) or
% outside the current tree (e.g., /etc/passwd)?
% a (any) : any file can be opened.
% r (restricted) : disallow opening dot files
% p (paranoid) : as `r' and disallow going to parent directories, and
% restrict absolute paths to be under $TEXMFOUTPUT.
openin_any = a
openout_any = p
--
David Kastrup
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 14:01:01 GMT)
Full text and
rfc822 format available.
Message #140 received at 31079 <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 14:15:02 GMT)
Full text and
rfc822 format available.
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
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 14:24:01 GMT)
Full text and
rfc822 format available.
Message #146 received at 31079 <at> debbugs.gnu.org (full text, mbox):
Hi Liyu and Ikumi and David,
> 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.
I think I indirectly suggested that modification? My apologies!
Thank you David and Ikumi, I've learned again something new.
J
Information forwarded
to
bug-auctex <at> gnu.org:
bug#31079; Package
auctex.
(Sun, 08 Apr 2018 14:37:01 GMT)
Full text and
rfc822 format available.
Message #149 received at 31079 <at> debbugs.gnu.org (full text, mbox):
>>>>> Liyu Gong <liyu.gong <at> uky.edu> writes:
> 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.
Glad to hear that. Cheers!
Ikumi Keita
Added tag(s) notabug.
Request was from
Arash Esbati <arash <at> gnu.org>
to
control <at> debbugs.gnu.org.
(Mon, 30 May 2022 09:03:01 GMT)
Full text and
rfc822 format available.
bug closed, send any further explanations to
31079 <at> debbugs.gnu.org and Liyu Gong <liyu.gong <at> uky.edu>
Request was from
Arash Esbati <arash <at> gnu.org>
to
control <at> debbugs.gnu.org.
(Mon, 30 May 2022 09:03:01 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org.
(Mon, 27 Jun 2022 11:24:10 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 304 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.