unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "John Wiegley" <johnw@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: 39724@debbugs.gnu.org
Subject: bug#39724: 26.3; Commit 44298ea6aa006ed227e539b02279bd3fc11fd2a6 breaks font display on macOS
Date: Sun, 23 Feb 2020 12:59:30 -0800	[thread overview]
Message-ID: <m2eeulggul.fsf@newartisans.com> (raw)
In-Reply-To: <20200221225014.GA49998@breton.holly.idiocy.org> (Alan Third's message of "Fri, 21 Feb 2020 22:50:14 +0000")

>>>>> "AT" == Alan Third <alan@idiocy.org> writes:

AT> Hi John, that commit isn’t in the emacs-27 branch, or if it is something
AT> has gone terribly wrong.

>> Anything prior to this works as expected. From this commit forward, all
>> windows are black on black.

You're right, I meant the master branch.

AT> Zhang Haijun has reported something similar on the master branch. The
AT> compile logs look as though there’s something wrong with his build
AT> environment. What version of macOS are you using? Are there any errors or
AT> warnings when you build it?

I'm using Catalina, let me capture the build log for you...

On a maybe related note, I now find that ERC is unusably slow: I can type
faster than Emacs can display the characters. Given that I've changed nothing
about my setup in past months, this could be related to other macOS changes.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2





  reply	other threads:[~2020-02-23 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 21:45 bug#39724: 26.3; Commit 44298ea6aa006ed227e539b02279bd3fc11fd2a6 breaks font display on macOS John Wiegley
2020-02-21 22:50 ` Alan Third
2020-02-23 20:59   ` John Wiegley [this message]
2020-02-24  9:45     ` Alan Third
2020-02-24 17:56       ` John Wiegley
2020-02-25 21:06         ` Alan Third
2020-03-05 17:22           ` Alan Third
2020-08-24  8:36             ` Stefan Kangas
2020-10-01 12:38               ` Stefan Kangas

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=m2eeulggul.fsf@newartisans.com \
    --to=johnw@gnu.org \
    --cc=39724@debbugs.gnu.org \
    --cc=alan@idiocy.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).