From: Eli Zaretskii <eliz@gnu.org>
To: Ari Roponen <ari.roponen@gmail.com>
Cc: 33442@debbugs.gnu.org
Subject: bug#33442: 26.1.90; Cairo side-by-side windows scrolling fix should be cherry-picked
Date: Tue, 20 Nov 2018 17:58:05 +0200 [thread overview]
Message-ID: <83wop7ivw2.fsf@gnu.org> (raw)
In-Reply-To: <87h8gc412q.fsf@gmail.com> (message from Ari Roponen on Tue, 20 Nov 2018 10:15:09 +0200)
> From: Ari Roponen <ari.roponen@gmail.com>
> Date: Tue, 20 Nov 2018 10:15:09 +0200
>
> Scrolling in --with-cairo -build doesn't work when there are
> side-by-side split windows. That was fixed in the master branch by
> commit 6e362a32bc9d21f73a0f29ca6f45481edeea6f29
>
> Author: Ari Roponen <ari.roponen@gmail.com>
> Date: Sun May 6 15:29:28 2018 +0300
>
> Fix cairo scrolling for side-by-side windows
>
> * src/xterm.c (x_scroll_run) [USE_CAIRO]: Fix scrolling for
> side-by-side split windows. (Bug#31288)
>
> Cherry-picking that commit fixes the problem in 26 branch too.
Thanks, but I'm not convinced we should backport that change. We
don't fix every bug on the release branch, only the important onces.
And the Cairo configuration doesn't strike me as important, what with
all the additional known bugs specific to it.
That said, I'm open to arguments to the contrary.
next prev parent reply other threads:[~2018-11-20 15:58 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 [this message]
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
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=83wop7ivw2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33442@debbugs.gnu.org \
--cc=ari.roponen@gmail.com \
/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).