From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ari.roponen@gmail.com, 33442@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#33442: 26.1.90; Cairo side-by-side windows scrolling fix should be cherry-picked
Date: Mon, 10 Dec 2018 14:23:06 +0100 [thread overview]
Message-ID: <m21s6pzfb9.fsf@gmail.com> (raw)
In-Reply-To: <87h8gc412q.fsf@gmail.com>
tags 33442 fixed
close 33442 26.2
quit
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Robert Pluim <rpluim@gmail.com>
>> I thought we were in a state on emacs-26 where we can get away with
>> cherry-picking minor fixes like the side-by-side stuff, precisely
>> because cairo is disabled by default. Also if any brave soul does
>> turn it on on emacs-26, we should probably strive to have fixed things
>> for them that are easy to fix.
>
> OK, please cherry-pick that part as well.
Done as 0220391c00
Closing this bug.
>> On a separate note, should we turn cairo on by default in master?
>
> I have no strong opinion on this. IMO, the decision should be based
> on what those who use Cairo say about its stability. I'd also
> encourage people to see whether the reported bugs are still there, or
> maybe they were solved indirectly.
I donʼt use it myself at the moment. Iʼve only seen Ari report that he
uses is regularly.
Robert
next prev parent reply other threads:[~2018-12-10 13:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 8:15 bug#33442: 26.1.90; Cairo side-by-side windows scrolling fix should be cherry-picked Ari Roponen
2018-11-20 15:58 ` Eli Zaretskii
2018-11-20 16:16 ` Dmitry Gutov
2018-11-20 17:14 ` Eli Zaretskii
2018-11-21 7:11 ` Ari Roponen
2018-11-21 21:40 ` Dmitry Gutov
2018-11-22 6:44 ` Ari Roponen
2018-11-22 12:03 ` Dmitry Gutov
2018-11-22 12:19 ` Ari Roponen
2018-11-22 14:05 ` Dmitry Gutov
2018-11-22 14:52 ` Eli Zaretskii
2018-11-22 15:22 ` Dmitry Gutov
2018-11-29 13:59 ` Dmitry Gutov
2018-11-29 12:15 ` Ari Roponen
2018-11-29 13:19 ` Robert Pluim
2018-11-29 14:06 ` Eli Zaretskii
2018-11-30 12:31 ` Ari Roponen
2018-12-08 9:55 ` Eli Zaretskii
2018-12-08 10:42 ` Dmitry Gutov
2018-12-08 11:15 ` Eli Zaretskii
2018-12-08 13:03 ` Dmitry Gutov
2018-12-08 14:24 ` Eli Zaretskii
2018-12-08 14:45 ` Dmitry Gutov
2018-12-09 22:08 ` Robert Pluim
2018-12-10 6:20 ` Eli Zaretskii
2018-12-10 13:23 ` Robert Pluim [this message]
2018-12-11 2:33 ` Dmitry Gutov
2018-12-11 3:37 ` Dmitry Gutov
2018-12-11 6:31 ` Eli Zaretskii
2018-12-11 6:27 ` Eli Zaretskii
2018-11-29 14:07 ` Dmitry Gutov
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=m21s6pzfb9.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=33442@debbugs.gnu.org \
--cc=ari.roponen@gmail.com \
--cc=dgutov@yandex.ru \
--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).