From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Porky Pig Newsgroups: gmane.emacs.help Subject: Re: a minor problem with AUCTEX. Please help. Date: Fri, 5 Mar 2010 16:25:04 -0800 (PST) Organization: http://groups.google.com Message-ID: <55aa16a2-4303-43d9-9267-d8aea0bd526d@m37g2000yqf.googlegroups.com> References: <3fc3ea80-b05a-4607-8c2e-502661b97e60@k22g2000vbp.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1272989638 2841 80.91.229.12 (4 May 2010 16:13:58 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 4 May 2010 16:13:58 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue May 04 18:13:57 2010 connect(): No such file or directory Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1O9Kkv-00012r-7s for geh-help-gnu-emacs@m.gmane.org; Tue, 04 May 2010 18:13:57 +0200 Original-Received: from localhost ([127.0.0.1]:58465 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O9Kku-0004Ir-Ex for geh-help-gnu-emacs@m.gmane.org; Tue, 04 May 2010 12:13:56 -0400 Original-Path: usenet.stanford.edu!postnews.google.com!m37g2000yqf.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 39 Original-NNTP-Posting-Host: 168.122.116.84 Original-X-Trace: posting.google.com 1267835104 908 127.0.0.1 (6 Mar 2010 00:25:04 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Sat, 6 Mar 2010 00:25:04 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: m37g2000yqf.googlegroups.com; posting-host=168.122.116.84; posting-account=JpxxPAgAAAAgwzQIYqn4j6syK-YhOmcF User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729), gzip(gfe), gzip(gfe) Original-Xref: usenet.stanford.edu gnu.emacs.help:177375 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:72917 Archived-At: On Jan 19, 12:16=A0pm, Leo wrote: > On 2010-01-18 22:00 +0000,PorkyPig wrote: > > > > > Hello, > > > I've been using EMACS+AUCTEXunder Windows XP for many years, with > > MikTeX, so I"m kind of familiar with its behavior. =A0A few days ago > > I've downloaded the latest EMACS for Windows (23.1.1) + the latest > >AUCTEX. Still Windows XP. Now the problem. I use Latex2E to process > > the .tex fils and create the dvi. Now when there is a compilation > > error, I press C-c C-` to look the error log. The screen gets split, > > the error logs shows up in the lower windows, *but* the upper part is > > empty. So I have to go to the buffer list and re-read the .tex file > > into the upper window. Then the file shows up, with a cursor pointing > > to the possible location of the error, as it should be. > > > Now with my old setup I had a similar situation on occasion: when > >AUCTEXcan't parse the error, so when I press C-c C-` I get the empty > > buffer. With my new setup, however, it happens all the time Latex2e > > detects the error. > > > I wonder whether there's someAUCTEXparameter I can tweak. > > > TIA. > > > (Note: I run portable MIKTEX, and I install and run EMACS+AUCTEXfrom > > the same USB flash drive. Other than that problem I've described, > > everything appears to work just fine, but, of course a bit slow.) > > There was some fix on this issue. Could you try theAUCTeXdevel version > from CVS? > > Leo Well, I've just download the latest build (86) of auctex (about two weks old), but the problem still persists. Apparently the fix if there *was* a fix, never found its way to the latest build. Oh well ...