From: Yasushi SHOJI <yashi@atmark-techno.com>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] cairo 6445ee0: Merge branch 'master' into cairo
Date: Wed, 20 May 2015 21:16:43 +0900 [thread overview]
Message-ID: <871tibsatw.wl@dns1.atmark-techno.com> (raw)
In-Reply-To: <555B4750.4030003@swipnet.se>
Hi,
On Tue, 19 May 2015 23:23:12 +0900,
Jan D. wrote:
>
> I can merge anytime. The only things I know about is lacking XBM
> support (not sure it is worth the effort), and the scrolling
> performance is not great. Possible there are some type of images that
> don't display right. But nothing major that prevents a merge.
Nothing major but:
- the current tip of the branch doesn't compile w/ --with-cairo. it
seems like git merge machinery messed some lines up. this should
be easy to fix.
- x_cr_destroy_surface() is not defined but used outside of USE_CAIRO
ifdef in src/xterm.c::handle_one_xevent(). this is also caused by
a merge commit fb77948660d9, which makes the tree unbuildable w/
--without-cairo.
- resizing emacs frame displays:
Gtk-CRITICAL **: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed
not sure why but it seems to display it when I make width narrower
than some criteria.
- make emacs frame much narrower cause "height width tool-tip at the
center of the frame (don't know how to call it)" start to "drop"
like rain drop in the frame, as if y value of the tool-tip is
radically changing. Also, the height of the frame gets larger.
just my 2 cents.
--
yashi @ debian unstable
next prev parent reply other threads:[~2015-05-20 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150517144706.20561.12321@vcs.savannah.gnu.org>
[not found] ` <E1YtzqP-0005Ma-6Z@vcs.savannah.gnu.org>
2015-05-18 17:43 ` [Emacs-diffs] cairo 6445ee0: Merge branch 'master' into cairo Stefan Monnier
2015-05-19 14:23 ` Jan D.
2015-05-19 18:40 ` Stefan Monnier
2015-05-23 10:49 ` Jan Djärv
2015-05-23 14:18 ` Stefan Monnier
2015-05-20 12:16 ` Yasushi SHOJI [this message]
2015-05-20 13:58 ` Stefan Monnier
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=871tibsatw.wl@dns1.atmark-techno.com \
--to=yashi@atmark-techno.com \
--cc=emacs-devel@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).