unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: pillule@riseup.net, 50112@debbugs.gnu.org,
	David Phillips <dphillips@cfa.harvard.edu>
Subject: bug#50112: 28.0.50; ediff help frame does not display text
Date: Sat, 21 Aug 2021 13:18:53 +0100	[thread overview]
Message-ID: <YSDvLRtwfSBAvKIC@breton.holly.idiocy.org> (raw)
In-Reply-To: <87pmu97e55.fsf@gnus.org>

On Thu, Aug 19, 2021 at 03:33:26PM +0200, Lars Ingebrigtsen wrote:
> David Phillips <dphillips@cfa.harvard.edu> writes:
> 
> > I built emacs this morning from the git master branch.
> > The latest commit was 9b31ad36094666da6b3281025adc163829d89de8 with
> > a date stamp of Wed Aug 18 20:02:39 2021 +0300.
> > I am running the macos GUI version.
> > First I run /Applications/Emacs/Contents/MacOS/Emacs -Q
> > then I load two files and run 'ediff-buffers' to compare them.
> > ediff works just fine except that the frame with the help message
> > is an empty frame. The '?' command changes the frame size but the
> > text never renders.
> 
> I can reproduce this problem on Macos, but not in Debian.
>
<snip>
> 
> Perhaps Alan has some insight here; added to the CCs.

This is a bit weird. When creating the graphics context to draw on we
need to specify a colorspace, so we just use the one that the (OS)
window we're drawing for uses.

However sometimes it seems we get a null from the window instead of a
legit colorspace which causes the graphics context creation to fail. I
don't know why we should ever get a null, but anyway, I've pushed a
change to master that should use a generic colorspace in these
situations.
-- 
Alan Third





  reply	other threads:[~2021-08-21 12:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 18:39 bug#50112: 28.0.50; ediff help frame does not display text David Phillips via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-19 13:33 ` Lars Ingebrigtsen
2021-08-21 12:18   ` Alan Third [this message]
2021-08-21 12:54     ` Lars Ingebrigtsen
2021-08-21 13:20     ` David Phillips via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-20  8:18 ` martin rudalics
2021-08-20 14:12   ` David Phillips via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-20 15:34     ` martin rudalics
2021-08-20 15:44       ` David Phillips via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=YSDvLRtwfSBAvKIC@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=50112@debbugs.gnu.org \
    --cc=dphillips@cfa.harvard.edu \
    --cc=larsi@gnus.org \
    --cc=pillule@riseup.net \
    /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).