unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Alan Mackenzie <acm@muc.de>, Glenn Morris <rgm@gnu.org>
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 11:43:16 -0700	[thread overview]
Message-ID: <36f4834d-4990-d22f-7b2b-78ebda9b7856@cs.ucla.edu> (raw)
In-Reply-To: <20170827170504.GG3520@ACM>

Alan Mackenzie wrote:
> On Sun, Aug 27, 2017 at 12:47:21 -0400, Glenn Morris wrote:
> 
>> If your system has the same issue with gcc warnings (and if you choose
>> not to answer the question, a cynic like me will assume it does), ...
su
> It does.

Then you'll need to fix your setup to get GCC working, as well as Emacs.


> Diagonal lines are the font's representation
> of ASCII grave (0x60), and arise from typing the key to the left of "1".

So this font cannot even display ASCII? Another annoyance. While you're fixing 
that you might as well fix the curved quotes.

I don't see this as rising to something that we need to worry about. Emacs is 
behaving consistently with other programs. Even with the display glitches, the 
batch diagnostics are still quite intelligible, so the glitches are merely an 
annoyance.

If despite my advice we decide to support this misconfigured font, then we need 
to change the default batch quoting style to 'straight', not 'grave'. This is 
because the font in question cannot display grave accent either. It would be a 
simple matter to use the 'straight' quoting style for all batch invocations. I'm 
not in favor of this, though.





  parent reply	other threads:[~2017-08-27 18:43 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 [this message]
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=36f4834d-4990-d22f-7b2b-78ebda9b7856@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=28242@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=rgm@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).