From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: 25987@debbugs.gnu.org
Subject: bug#25987: 25.2; support gcc fixit notes
Date: Wed, 08 Mar 2017 21:22:35 +0200 [thread overview]
Message-ID: <837f3zh8uc.fsf@gnu.org> (raw)
In-Reply-To: <87a88v7h35.fsf@tromey.com> (message from Tom Tromey on Wed, 08 Mar 2017 11:34:38 -0700)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>, 25987@debbugs.gnu.org
> Date: Wed, 08 Mar 2017 11:34:38 -0700
>
> Tom> I'll see if I can find out the rationale.
>
> Eli> Thanks.
>
> The reason is compatibility with clang, which had this option first.
> http://releases.llvm.org/3.8.0/tools/clang/docs/UsersManual.html#cmdoption-fdiagnostics-parseable-fixits
Thanks. So maybe GCC should have a similar option, named differently,
which would report in characters.
Anyway, "we have the technology" in Emacs to deal with this.
next prev parent reply other threads:[~2017-03-08 19:22 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 [this message]
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
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=837f3zh8uc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25987@debbugs.gnu.org \
--cc=tom@tromey.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).