Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!jr@bbn.com
From: jr@bbn.com (John Robinson)
Newsgroups: comp.emacs
Subject: Re: Line numbers
Message-ID: <39182@bbn.COM>
Date: 27 Apr 89 15:05:48 GMT
References: <39135@bbn.COM> <2201@pur-phy>
Sender: news@bbn.COM
Reply-To: jr@bbn.com (John Robinson)
Organization: BBN Systems and Technologies Corporation, Cambridge MA
Lines: 32
In-reply-to: sho@pur-phy (Sho Kuwamoto)

In article <2201@pur-phy>, sho@pur-phy (Sho Kuwamoto) writes:
>In article <39135@bbn.COM> dpaulso@RELAY.NSWC.NAVY.MIL writes:
><the best thing to do is to run your compiles from inside emacs, using 
><M-x compile.  documentation for this function follows:
>< [...]
><  You can then use the command C-x ` to find the next error message
><  and move to the source code that caused it.
>
>This doesn't seem to work very well with TeX.  First, M-x compile
>doesn't seem to run your compile in an interactive shell.  (could be
>wrong about this one)  Second, it has trouble parsing the TeX error
>messages.  I usually just run it in a shell window and use 
>M-x < C-u # C-n.  Pretty gross, but it seems to work.
>
>-Sho

To integrate TeX with Emacs' compile/next-error mechanism:

(1) run TeX non-interactively:

\scrollmode or \batchmode near the top of the file;

(2) write the elisp code (non-trivial, I fear) to make next-error work
on TeX error output.

If you undertake #2, you might want to reorganize it to scan the
*shell* buffer instead, then you don't have to do #1, and can run TeX
interactively if you feel like it (or do part of it interactively).
--
/jr
jr@bbn.com or bbn!jr
C'mon big money!