From: Andreas Politz <politza@fh-trier.de>
To: help-gnu-emacs@gnu.org
Subject: Re: AUCtex & Errors while compiling
Date: Sat, 17 Apr 2010 01:20:25 +0200 [thread overview]
Message-ID: <87aat36l3a.fsf@fh-trier.de> (raw)
In-Reply-To: 4bc8c5a6$0$6893$9b4e6d93@newsspool2.arcor-online.net
Claudius Hubig <claudiushubig@arcor.de> writes:
> Hello Andreas,
>
> Andreas Politz <politza@fh-trier.de> wrote:
>>Claudius Hubig <claudiushubig@arcor.de> writes:
>>> Compiling also works fine, but when it encounters an error, it tells
>>> me to press C-c `. Being on a German keyboard with deadkeys enabled,
>>> I first press C-c, then Shift-' (key left of backspace) and then
>>> space. It then asks me for a master file:
>>M-g n
>>also works.
>
> Thank you :)
>
>>> Is there now any way to
>>> a) get my original file automatically into the buffer on the left and
>>> b) get "links" from the "faulty" lines mentioned on the right to the
>>> corresponding lines on the left?
>>This sounds like what actually should happen.
>>> (setq-default TeX-master nil);
>>Try to change `nil' with `t', and see if it helps (Needs restart), or
>
> Thank you again. Now at least the first part is done – though there's
> no “nice” linking between the errors and the lines yet, as possible
> with C++ & 'compile, where I get a window with a list of errors which
> are coloured and underlined and when I press RET on one of these, it
> takes me to the appropriate line in the source file.
>
> Is this possible with TeX or should I take what I get and be happy? :)
Yes, the `linking'. AUCtex does not play by the rules in this case and
uses it's own display-error-foo.
-ap
>
> Best regards,
>
> Claudius
next prev parent reply other threads:[~2010-04-16 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 18:22 AUCtex & Errors while compiling Claudius Hubig
2010-04-16 19:37 ` Andreas Politz
2010-04-16 20:16 ` Claudius Hubig
2010-04-16 23:20 ` Andreas Politz [this message]
2010-04-17 12:34 ` Ralf Angeli
2010-04-17 12:26 ` Ralf Angeli
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aat36l3a.fsf@fh-trier.de \
--to=politza@fh-trier.de \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).