From: Jan Nieuwenhuizen <janneke@gnu.org>
To: emacs-devel <emacs-devel@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: compilation-mode support for Guile backtrace; v2 much simplified
Date: Fri, 8 Aug 2014 19:51:04 +0200 [thread overview]
Message-ID: <1407520265-23162-1-git-send-email-janneke@gnu.org> (raw)
Hi,
Here's a much simplified and collapsed version of compilation-mode
support for Guile backtraces.
In short:
-no resolving trickery of absolute file names, we'll try
to do that upstream
-remaining are the two non-GNU standard Guile convention regexpses
It would be nice we can have Guile-2.2 use GNU-standard error messages
in backtraces, but either way we'll probably have to live with current
guile backtraces for quite some time.
Greetings, Jan
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
next reply other threads:[~2014-08-08 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 17:51 Jan Nieuwenhuizen [this message]
2014-08-08 17:51 ` [PATCH] Support Guile backtraces in compilation mode Jan Nieuwenhuizen
2014-08-09 1:40 ` Stefan Monnier
2014-08-09 7:30 ` Jan Nieuwenhuizen
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1407520265-23162-1-git-send-email-janneke@gnu.org \
--to=janneke@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=guile-devel@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).