From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, Paul Eggert <eggert@cs.ucla.edu>, 28242@debbugs.gnu.org
Subject: bug#28242: Batch mode compiling: Error messages are displayed with "invalid character" glyph bounding symbols.
Date: Thu, 20 Aug 2020 17:59:58 +0200 [thread overview]
Message-ID: <87wo1tqpdt.fsf@gnus.org> (raw)
In-Reply-To: <83o9r0523n.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 27 Aug 2017 20:53:32 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> What if the output of Emacs is
>> being sent to a file or pipe, and some other program later displays the text?
>
> I don't think we should care. The primary goal is to have batch-mode
> messages to the screen display legibly. If another program later
> examines the results, it's a problem for that other program. In
> particular, if that other program is Emacs, we already have the
> solution for displaying these quotes in interactive sessions.
If I skim this thread correctly, I think the general sentiment was that
this wasn't something that should be fixed, so I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-20 15:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 13:06 bug#28242: Batch mode compiling: Error messages are displayed with "invalid character" glyph bounding symbols Alan Mackenzie
2017-08-26 14:09 ` Eli Zaretskii
2017-08-26 17:06 ` Alan Mackenzie
2017-08-26 18:12 ` Eli Zaretskii
2017-08-26 19:24 ` Alan Mackenzie
2017-08-26 19:40 ` Eli Zaretskii
2017-08-26 20:39 ` Alan Mackenzie
2017-08-27 8:16 ` Paul Eggert
2017-08-27 9:16 ` Alan Mackenzie
2017-08-27 14:40 ` Eli Zaretskii
2017-08-27 16:46 ` Paul Eggert
2017-08-27 17:23 ` Alan Mackenzie
2017-08-27 17:53 ` Eli Zaretskii
2020-08-20 15:59 ` Lars Ingebrigtsen [this message]
2017-08-27 16:40 ` Paul Eggert
2017-08-27 16:56 ` Alan Mackenzie
2017-08-27 16:47 ` Glenn Morris
2017-08-27 17:05 ` Alan Mackenzie
2017-08-27 17:21 ` Eli Zaretskii
2017-08-27 17:31 ` Alan Mackenzie
2017-08-27 17:50 ` Eli Zaretskii
2017-08-27 18:43 ` Paul Eggert
2017-08-27 19:04 ` Alan Mackenzie
2017-08-27 21:38 ` Paul Eggert
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=87wo1tqpdt.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=28242@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eggert@cs.ucla.edu \
--cc=eliz@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.
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).