Ralf Angeli <[EMAIL PROTECTED]> writes: > * David Kastrup (2008-02-16) writes: > >> This is all such an unreliable mess. Perhaps our file name recorder >> should never forget any file and just record the name and the purported >> nesting. > > With "file" you probably mean anything in parentheses. > >> And when an error occurs, it checks every recorded file name >> in some intelligent order, preferring loaded files over non-loaded ones >> and ignoring non-existent pseudo-files, and then using the first match >> for the error context lines. > > Hm, with a lot of rubbish on the file name stack this might even > increase the probability of false matches.
I don't see how that matters. "some intelligent order" means that the "lot of rubbish" comes into play only once the stuff we check right now has failed to come up with a matching line. So we are at worst getting false matches where previously we got no match at all. >> Or tell people to configure file-line error messages. > > How about we actually make this the default as also Richard proposed? > If people use TeX engines not aware of the -file-line-error option, > would they abort when encountering it? I just tried with > $ pdftex --version > pdfTeX using libpoppler 3.141592-1.40.3-2.2 (Web2C 7.5.6) > kpathsea version 3.5.6 > and this processes a file even if given an unrecognized command line > argument. It only complains like this: > latex: unrecognized option `--foo' I think I am almost more worried about the engines that understand it. Earlier versions of that option omitted the usual TeX error context altogether. AUCTeX will not understand those messages, and preview-latex has no chance to guess the originating column then. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum _______________________________________________ bug-auctex mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-auctex
