Trevor Spiteri <[email protected]> writes: > If I have a tex file with an error, TeX-next-error will open a buffer > named "MiKTeX 2.8" and go to that buffer instead of taking me to the > error in the file. > > I used a file named c:\Users\Trevor\Home\delme\a.tex with the contents > (containing an error): > \documentclass{article} > \begin{document} > \nocommand > \end{document} > > The output buffer has the following contents: > > Running `LaTeX' on `a' with ``pdflatex -interaction=nonstopmode > "\input" "a.tex"'' > This is pdfTeX, Version 3.1415926-1.40.10 (MiKTeX 2.8) > entering extended mode > LaTeX2e <2009/09/24> > Babel <v3.8l> and hyphenation patterns for english, dumylang, > nohyphenation, german, ngerman, german-x-2009-06-19, > ngerman-x-2009-06-19, french, loaded. > (c:\Users\Trevor\Home\delme\a.tex > ("C:\Program Files (x86)\MiKTeX 2.8\tex\latex\base\article.cls" > Document Class: article 2007/10/19 v1.4h Standard LaTeX document class > ("C:\Program Files (x86)\MiKTeX 2.8\tex\latex\base\size10.clo"))
The directory "Program Files (x86)" has a file name that directly clashes with the file opening message format of TeX. I recommend that you try seeing whether MikTeX allows you to set the -file-line-error option globally. That picks a different error message format that might make TeX's diagnostic messages be less likely confused with your directory names. -- David Kastrup _______________________________________________ bug-auctex mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-auctex
