From: Paul Eggert <eggert@cs.ucla.edu>
To: Alan Mackenzie <acm@muc.de>
Cc: 28242@debbugs.gnu.org
Subject: bug#28242: Batch mode compiling: Error messages are displayed with "invalid character" glyph bounding symbols.
Date: Sun, 27 Aug 2017 14:38:12 -0700 [thread overview]
Message-ID: <cb2a14e4-9dea-ccf6-1b14-be8564668c5f@cs.ucla.edu> (raw)
In-Reply-To: <20170827190404.GJ3520@ACM>
Alan Mackenzie wrote:
>> Then you'll need to fix your setup to get GCC working, as well as Emacs.
>
> I will get around to that in good time.
When that happens, the issue should be fixed for both GCC and Emacs, even in an
UTF-8 locale.
> It remains a problem for all
> those working with the standard Linux font.
It is by no means the "standard" font. Hardly anybody uses it on Linux any more.
I have to go to some work to try it out myself, on either Ubuntu or Fedora. The
few people who use Linux console fonts are generally aware of these issues and
it is not hard to address them.
> There was a time when Emacs was a leader, not a follower.
In this case the issue seems to be whether Emacs should "lead" us back to the
1980s, when PCs had inferior fonts.
> Stop being idiotic.
It is not at all an idiotic suggestion. ISO 646 permits countries to usurp grave
accent. For example, old-design French monitors display grave accent as a micro
sign (µ), to conform to the French NF Z 62-010 profile for ISO 646. Again, I
don't think Emacs should take trouble to cater to old designs like this.
However, if we do it then it's safer and more portable for Emacs to avoid
routine use of grave accent in its batch diagnostics, as grave accent is
mishandled more often than apostrophe is. This is because ISO 646 usurps grave
accent but not apostrophe.
> How about allowing the user to configure this
It is configurable already; just set LC_ALL=C in the environment. This should
fix the issue for both Emacs and GCC.
PS. Rhetoric like "Stop being idiotic" is not helpful here.
prev parent reply other threads:[~2017-08-27 21:38 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
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 [this message]
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=cb2a14e4-9dea-ccf6-1b14-be8564668c5f@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=28242@debbugs.gnu.org \
--cc=acm@muc.de \
/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.