I have recursive makefiles that I run to build my large tree which has many 100's of latex files (I use latex for everything). These makefiles travel the tree and build pdf's and generate HTML files using htlatex.
The problem I have is when there is an error, it is always very hard for me to find which file actually caused this error.
For some reason, Latex does not show the file name, only the error and the line number.
This is something I always found very strange. How hard is it to give the file name as well?
For example, here is an error I have now:
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsa.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsb.fd)
! Missing \endcsname inserted.
<to be read again>
\protect
l.88 \end{tabularx}
So now I try to find the file name by scrolling up the terminal. But there is so much output generated, many times it takes me long minutes searching up and down the buffer just to find the latex command in order to find which file was being compiled when the error occurred.
Is there an option to either just tell latex/pdflatex to only show the actual command used and not all other logging it does to make it easy to see the command, or better, is there a way to tell it to show the file name in addition to the line number?
using texliver 2012 debian based.
pdflatex --file-line-error <filename>– egreg May 26 '13 at 08:46index.tex:88does not help me too much to find whichindex.texit is. Thanks for your hint, I found this command line options here http://linuxcommand.org/man_pages/pdflatex1.html but do not see another option now to show the full path. But will keep looking – Nasser May 26 '13 at 08:56--file-line-error --output-directory="<currentdir>"– karlkoeller May 26 '13 at 09:35myfile.texin the directoryC:\mydirmy full command line ispdflatex --file-line-error --output-directory="C:/mydir" myfile.tex. Note that if I don't specify.texit doesn't work. – karlkoeller May 26 '13 at 10:48myfile.texin/usr/share/mydir, probablypdflatex --file-line-error --output-directory="/usr/share/mydir" myfile.texmay work in your case (or something similar). – karlkoeller May 26 '13 at 10:52