From: Porky Pig <porky_pig_jr@my-deja.com>
To: help-gnu-emacs@gnu.org
Subject: a minor problem with AUCTEX. Please help.
Date: Mon, 18 Jan 2010 14:00:46 -0800 (PST) [thread overview]
Message-ID: <3fc3ea80-b05a-4607-8c2e-502661b97e60@k22g2000vbp.googlegroups.com> (raw)
Hello,
I've been using EMACS+AUCTEX under Windows XP for many years, with
MikTeX, so I"m kind of familiar with its behavior. A 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
AUCTEX can'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 some AUCTEX parameter I can tweak.
TIA.
(Note: I run portable MIKTEX, and I install and run EMACS+AUCTEX from
the same USB flash drive. Other than that problem I've described,
everything appears to work just fine, but, of course a bit slow.)
next reply other threads:[~2010-01-18 22:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 22:00 Porky Pig [this message]
2010-01-19 17:16 ` a minor problem with AUCTEX. Please help Leo
[not found] ` <mailman.1712.1263921615.18930.help-gnu-emacs@gnu.org>
2010-01-19 20:14 ` Porky Pig
2010-01-20 9:07 ` David Kastrup
2010-01-21 19:52 ` Leo
[not found] ` <mailman.1894.1264103574.18930.help-gnu-emacs@gnu.org>
2010-01-21 19:54 ` David Kastrup
2010-01-22 20:40 ` Porky Pig
2010-01-23 0:26 ` Leo
2010-01-23 0:36 ` Leo
2010-01-21 1:55 ` Porky Pig
2010-01-21 20:03 ` Leo
2010-03-06 0:25 ` Porky Pig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3fc3ea80-b05a-4607-8c2e-502661b97e60@k22g2000vbp.googlegroups.com \
--to=porky_pig_jr@my-deja.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.