From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ivan-p-sokolov@ya.ru, 49609@debbugs.gnu.org
Subject: bug#49609: [PATCH] Add option for handling SGR control sequences in compilation-mode
Date: Mon, 19 Jul 2021 18:45:29 +0300 [thread overview]
Message-ID: <834kcq71eu.fsf@gnu.org> (raw)
In-Reply-To: <87zguio1ex.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 19 Jul 2021 15:53:26 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Ivan Sokolov <ivan-p-sokolov@ya.ru>, 49609@debbugs.gnu.org
> Date: Mon, 19 Jul 2021 15:53:26 +0200
>
> >> >> +If the symbol `filter', then filter all SGR control sequences.
> >> >
> >> > Perhaps this should say what "SGR" is?
> >>
> >> One of the ANSI escape sequences.
> >
> > SGR = Select Graphic Rendition.
>
> I see. And these are control sequences that are output by... gcc? As
> opposed to ... other ANSI escape sequences?
No, these two terms are synonyms, AFAIK. GCC doesn't emit any SGR
sequences that other similar applications, like Grep, don't. They are
just sequences to produced colors and other attributes: bold,
underline, etc. The intent is to make the important parts of the
output easier to spot.
next prev parent reply other threads:[~2021-07-19 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 19:37 bug#49609: [PATCH] Add option for handling SGR control sequences in compilation-mode Ivan Sokolov
2021-07-17 19:48 ` Ivan Sokolov
2021-07-18 0:18 ` Lars Ingebrigtsen
2021-07-18 0:45 ` Ivan Sokolov
2021-07-18 6:52 ` Eli Zaretskii
2021-07-19 13:53 ` Lars Ingebrigtsen
2021-07-19 15:45 ` Eli Zaretskii [this message]
2021-07-19 15:53 ` Lars Ingebrigtsen
2021-07-19 16:38 ` Eli Zaretskii
2021-07-19 16:55 ` Lars Ingebrigtsen
2021-07-19 17:20 ` Eli Zaretskii
2021-07-19 21:47 ` Ivan Sokolov
2021-07-20 11:35 ` Lars Ingebrigtsen
2021-07-19 20:19 ` Ivan Sokolov
2021-07-17 20:57 ` Jim Porter
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834kcq71eu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49609@debbugs.gnu.org \
--cc=ivan-p-sokolov@ya.ru \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.