From: Nordlöw <per.nordlow@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Getting the "explanation" part of the current error message
Date: Wed, 27 Jan 2010 04:24:04 -0800 (PST) [thread overview]
Message-ID: <290eb05e-504b-4a8a-8ce2-5c9fed9851a3@k35g2000yqb.googlegroups.com> (raw)
Hi!
I'm looking for a way to take the "explanation" part of a (GCC or
other) compilation info/warning/error message and display it
separately in the minibuffer or as a tooltip near the problem source
code line.
I have looked at the sources simple.el compile.el specifically at
compilation-next-error-function() but I don't find any structure that
contains the (pre-)parsed messages of the compilation-buffer contents.
Does such a structure exists? If so we could extended it with the
"explanation" part and visualize in next-error-hook. If not I guess we
need to use compilation-error-regexp-alist-alist and to separately
parse the compilation-buffer, right?
/Nordlöw
next reply other threads:[~2010-01-27 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 12:24 Nordlöw [this message]
2010-01-27 14:00 ` Getting the "explanation" part of the current error message Kevin Rodgers
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=290eb05e-504b-4a8a-8ce2-5c9fed9851a3@k35g2000yqb.googlegroups.com \
--to=per.nordlow@gmail.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.
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).