From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28242@debbugs.gnu.org
Subject: bug#28242: Batch mode compiling: Error messages are displayed with "invalid character" glyph bounding symbols.
Date: Sat, 26 Aug 2017 17:06:59 +0000 [thread overview]
Message-ID: <20170826170659.GC5508@ACM> (raw)
In-Reply-To: <83k21q5sky.fsf@gnu.org>
Hello, Eli.
On Sat, Aug 26, 2017 at 17:09:17 +0300, Eli Zaretskii wrote:
> > Date: Sat, 26 Aug 2017 13:06:08 +0000
> > From: Alan Mackenzie <acm@muc.de>
> >
> > On my new PC (Gentoo GNU/Linux), byte compiling in batch mode (e.g. with
> > make bootstrap in the master branch) is displaying warning messages with
> > symbols "quoted" by the invalid character glyph (a solid square) rather
> > than ` and '. Presumably Emacs is attempting to use single curly
> > quotes.
> >
> > This is ugly and not helpful. A fix would be appreciated.
> You need to figure out why the logic in startup--setup-quote-display
> isn't working in your case.
I don't think the calling of that function is pertinent; there is only
one call of it, and that is inside "(unless noninteractive ...)".
Presumably noninterative will be non-nil in batch mode.
Perhaps the problem is that that function (or some equivalent) isn't
being called, and Emacs is outputting non-displayable characters
regardless.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-08-26 17:06 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 [this message]
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
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=20170826170659.GC5508@ACM \
--to=acm@muc.de \
--cc=28242@debbugs.gnu.org \
--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).