From: Eli Zaretskii <eliz@gnu.org>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: cpitclaudel@gmail.com, emacs-devel@gnu.org
Subject: Re: Some observations about --with-cairo
Date: Fri, 29 Sep 2017 11:49:38 +0300 [thread overview]
Message-ID: <83wp4h99el.fsf@gnu.org> (raw)
In-Reply-To: <wlo9pxhioa.wl%mituharu@math.s.chiba-u.ac.jp> (message from YAMAMOTO Mitsuharu on Tue, 26 Sep 2017 19:13:09 +0900)
> Date: Tue, 26 Sep 2017 19:13:09 +0900
> From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> Cc: emacs-devel@gnu.org
>
> > Is there a roadmap / task list somewhere?
>
> Roughly speaking, the current cairo code is based on my old code in
>
> http://lists.gnu.org/archive/html/emacs-devel/2009-04/msg00096.html
>
> and Jan's double-buffering code that draws into an image surface. I
> think a possible next step would be to see if one can drop the latter
> and use Daniel's Xdbe code instead as in the Xlib version. If this
> works, then it will make the cairo code simpler and more maintainable.
I'm okay with going with your proposal, but please note that XDBE
support has a few bugs of its own, which are not being worked on
either. So, while going with your proposal would probably make
maintenance easier, my main concern is that I don't currently see
anyone maintaining either of these two features, at least not as far
as fixing known bugs is concerned.
So I'm not sure your proposal will improve the situation with the bugs
related to these 2 features, unfortunately. And without fixing these
bugs, we cannot in good faith claim these features are supported as
everything else in Emacs is.
prev parent reply other threads:[~2017-09-29 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 20:03 Some observations about --with-cairo David Kastrup
2017-09-24 14:11 ` Clément Pit-Claudel
2017-09-25 12:51 ` Noam Postavsky
2017-09-25 14:12 ` Robert Pluim
2017-09-25 14:38 ` Noam Postavsky
2017-09-26 10:13 ` YAMAMOTO Mitsuharu
2017-09-29 8:49 ` Eli Zaretskii [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
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=83wp4h99el.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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).