unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Aaron Jensen <aaronjensen@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: 30699@debbugs.gnu.org
Subject: bug#30699: 26.0.91; buffer contents flicker on macOS frames when frames are resized
Date: Sun, 4 Mar 2018 18:06:13 -0800	[thread overview]
Message-ID: <CAHyO48xNhvkOzkHujPUv=KheyGrSK3ZNMkpO3yjhh3AnghDfGQ@mail.gmail.com> (raw)
In-Reply-To: <20180304213404.GB1479@breton.holly.idiocy.org>

On Sun, Mar 4, 2018 at 1:34 PM, Alan Third <alan@idiocy.org> wrote:
>> Simpler repro:
>>
>> (dotimes (n 10)
>>   (set-frame-parameter nil 'width (+ 80 n))
>>   (sit-for 0.1))
>>

Thank you, that's much easier :)

> The attached patch appears to fix it without breaking mouse resizing,
> but it looks like this comment in windowDidResize also counts for macOS:

This patch appears to fix it for me, it's much nicer, thank you!

I tested it with my keyboard resizing and mouse resizing and all seems
to work well.

Is this too dangerous of a patch to apply to emacs-26? The main case
I'd make for it is these new posframe libraries are really nice, so
it'd be nice for non-HEAD users to be able to use them w/o the
flicker.

Thanks!





  reply	other threads:[~2018-03-05  2:06 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-04 17:38 bug#30699: 26.0.91; buffer contents flicker on macOS frames when frames are resized Aaron Jensen
2018-03-04 20:27 ` Alan Third
2018-03-04 21:34   ` Alan Third
2018-03-05  2:06     ` Aaron Jensen [this message]
2018-03-05  3:27       ` Eli Zaretskii
2018-03-05  5:21         ` Aaron Jensen
2018-03-05 16:01           ` Eli Zaretskii
2018-03-05 16:21             ` Aaron Jensen
2018-03-05 18:00               ` Eli Zaretskii
2018-03-05 19:23                 ` Alan Third
2018-03-05 19:53                   ` Eli Zaretskii
2018-03-06 22:55                     ` Alan Third
2018-03-07 17:26                       ` Eli Zaretskii
2018-03-07 20:26                         ` Alan Third
2018-03-08 19:15                           ` Eli Zaretskii
2018-03-09 12:09                             ` Alan Third
2018-03-09 13:32                               ` Eli Zaretskii
2018-03-09 23:24                                 ` Alan Third
2018-03-10  0:25                                   ` Alan Third
2018-03-10  1:18                                     ` Aaron Jensen
2018-03-10  8:30                                     ` Eli Zaretskii
2018-03-10 23:07                                       ` Alan Third
2018-03-11 16:29                                         ` Eli Zaretskii
2018-03-12  0:46                                           ` Alan Third
2018-03-12 16:39                                             ` Eli Zaretskii
2018-03-12 23:42                                               ` Alan Third
2018-03-13 12:19                                                 ` Alan Third
2018-03-13 16:56                                                   ` Eli Zaretskii
2018-03-13 20:18                                                     ` Alan Third
2018-03-13 15:34                                             ` Aaron Jensen
2018-03-14 15:08                                               ` Alan Third
2018-03-19 15:15                                                 ` Alan Third
2018-03-19 15:27                                                   ` Eli Zaretskii
2018-03-19 17:19                                                     ` Alan Third
2018-03-20 21:50                                                       ` Aaron Jensen
2018-03-20 23:22                                                         ` Aaron Jensen
2018-03-21  6:32                                                         ` Eli Zaretskii
2018-03-21 16:27                                                           ` Aaron Jensen
2018-03-10  8:15                                   ` Eli Zaretskii
2018-03-05  7:55     ` Aaron Jensen
2018-03-05 16:12       ` Eli Zaretskii
2018-03-06 23:00       ` Alan Third
2018-03-07 17:26         ` Eli Zaretskii

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='CAHyO48xNhvkOzkHujPUv=KheyGrSK3ZNMkpO3yjhh3AnghDfGQ@mail.gmail.com' \
    --to=aaronjensen@gmail.com \
    --cc=30699@debbugs.gnu.org \
    --cc=alan@idiocy.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).