From: Eli Zaretskii <eliz@gnu.org>
To: David Malcolm <dmalcolm@redhat.com>
Cc: 25987@debbugs.gnu.org
Subject: bug#25987: 25.2; support gcc fixit notes
Date: Tue, 13 Oct 2020 17:37:54 +0300 [thread overview]
Message-ID: <83362i2nul.fsf@gnu.org> (raw)
In-Reply-To: <26f277bb345f10efe6340ac4074960905064fc97.camel@redhat.com> (message from David Malcolm on Mon, 12 Oct 2020 18:27:29 -0400)
> From: David Malcolm <dmalcolm@redhat.com>
> Cc: 25987@debbugs.gnu.org
> Date: Mon, 12 Oct 2020 18:27:29 -0400
>
> I like how -fdiagnostics-parseable-fixits adds extra lines of output,
> with a prefix that's ought to be easy to detect.
Yes, I think that's preferable, indeed.
> BTW, does Emacs set anything in the environment that GCC could detect?
Yes, Emacs sets INSIDE_EMACS when it runs a sub-process.
> Does Emacs have an automated test suite that could test this feature?
Yes, see the tests in the test/ subdirectory of the Emacs tree.
> Another complication to consider: the locations in a fix-it hint refer
> to the original source file, before any changes are made. If the user
> interface supports the user e.g. clicking on fix-it hints and
> selectively apply them one by one, then after each fix-it hint is
> applied, all locations after that point potentially need to be "fixed
> up" somehow, to reflect the changes to the buffer.
That could be handled automatically by defining a marker at each
hint's location, then they will move as text is edited.
next prev parent reply other threads:[~2020-10-13 14:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 21:47 bug#25987: 25.2; support gcc fixit notes Tom Tromey
2017-03-06 18:35 ` Eli Zaretskii
2017-03-07 13:54 ` Tom Tromey
2017-03-07 15:55 ` Eli Zaretskii
2017-03-08 18:34 ` Tom Tromey
2017-03-08 19:22 ` Eli Zaretskii
2017-03-09 4:20 ` Richard Stallman
2017-03-09 15:36 ` Eli Zaretskii
2017-03-08 18:44 ` Tom Tromey
2017-03-08 19:28 ` Eli Zaretskii
2017-03-09 16:37 ` Dmitry Gutov
2017-03-09 16:56 ` Eli Zaretskii
2017-03-09 17:37 ` Dmitry Gutov
2017-03-09 18:32 ` Eli Zaretskii
2017-03-09 21:26 ` Dmitry Gutov
2017-08-06 3:34 ` Tom Tromey
2017-03-09 16:18 ` Dmitry Gutov
2017-03-09 16:53 ` Eli Zaretskii
2017-03-09 17:49 ` Dmitry Gutov
2017-03-09 18:35 ` Eli Zaretskii
2017-08-06 3:31 ` Tom Tromey
2018-03-16 16:48 ` David Malcolm
2018-03-16 20:19 ` Eli Zaretskii
2020-10-06 18:17 ` David Malcolm
2020-10-06 18:37 ` Eli Zaretskii
2020-10-12 22:27 ` David Malcolm
2020-10-13 7:34 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-13 14:37 ` Eli Zaretskii [this message]
2020-10-14 22:43 ` David Malcolm
2020-10-15 7:47 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-14 21:37 ` David Malcolm
2020-10-15 13:53 ` Eli Zaretskii
2020-10-15 14:23 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-15 14:29 ` Eli Zaretskii
2020-10-15 14:44 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-20 14:52 ` David Malcolm
2020-10-20 15:54 ` Eli Zaretskii
2020-11-11 19:36 ` David Malcolm
2020-11-12 13:54 ` Eli Zaretskii
2020-11-13 16:47 ` David Malcolm
2020-11-14 14:21 ` Eli Zaretskii
2020-11-14 19:46 ` David Malcolm
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=83362i2nul.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25987@debbugs.gnu.org \
--cc=dmalcolm@redhat.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).