From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: alan@idiocy.org, 30800@debbugs.gnu.org
Subject: bug#30800: 26.0.91; unknown crash on macos
Date: Thu, 22 Mar 2018 09:26:50 +0200 [thread overview]
Message-ID: <834ll8k1tx.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48wn2dn4VfOmi03RCXCfWvV-hmfF=MBTTHPqmPeUMH8eoA@mail.gmail.com> (message from Aaron Jensen on Wed, 21 Mar 2018 22:40:33 -0700)
> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Wed, 21 Mar 2018 22:40:33 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>, 30800@debbugs.gnu.org
>
> > (Original bug report was 18757 and the commit was
> > d9d383147219f8e6a90d4c177e1b454e19acfac9.)
>
> I do not understand why setting the represented filename where it was
> set originally causes a flicker.
I don't understand, either, especially since I don't see this on w32.
The recipes in bug#18757 seem to indicate that redisplaying the
frame's title, due to the change in the selected buffer, causes the
flickering. That flickering started happening with the upgrade to
version 10.10 of the OS, so perhaps it's no linger an issue with the
current OS versions?
> It's probably a dumb question, but would using the start/stop paint
> stuff from the flicker bug help to eliminate the flicker in some way?
Do you still see the flicker if you revert the above commit?
next prev parent reply other threads:[~2018-03-22 7:26 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 16:18 bug#30800: 26.0.91; unknown crash on macos Aaron Jensen
2018-03-13 16:36 ` Aaron Jensen
2018-03-20 23:39 ` Aaron Jensen
2018-03-21 6:37 ` Eli Zaretskii
2018-03-21 16:25 ` Aaron Jensen
2018-03-21 17:00 ` Eli Zaretskii
2018-03-21 17:09 ` Eli Zaretskii
2018-03-21 17:31 ` Aaron Jensen
2018-03-21 18:22 ` Eli Zaretskii
2018-03-21 18:31 ` Aaron Jensen
2018-03-21 18:48 ` Eli Zaretskii
2018-03-21 19:19 ` Alan Third
2018-03-21 19:36 ` Eli Zaretskii
2018-03-21 20:12 ` Alan Third
2018-03-22 5:40 ` Aaron Jensen
2018-03-22 7:26 ` Eli Zaretskii [this message]
2018-03-22 15:39 ` Aaron Jensen
2018-03-22 15:57 ` Eli Zaretskii
2018-03-23 1:49 ` Aaron Jensen
2018-03-23 8:16 ` Eli Zaretskii
2018-03-23 19:52 ` Alan Third
2018-03-23 20:57 ` Aaron Jensen
2018-03-24 7:20 ` Aaron Jensen
2018-03-24 10:29 ` Alan Third
2018-03-24 14:54 ` Eli Zaretskii
2018-03-24 16:18 ` Alan Third
2018-03-24 17:48 ` Eli Zaretskii
2018-03-25 19:17 ` Alan Third
2018-03-24 10:49 ` Charles A. Roelli
2018-03-24 14:12 ` Alan Third
2018-03-25 20:14 ` Charles A. Roelli
2018-03-26 18:37 ` Alan Third
2018-03-26 23:03 ` Aaron Jensen
2018-03-30 11:37 ` Alan Third
2018-03-30 11:57 ` Aaron Jensen
2018-03-22 5:35 ` Aaron Jensen
2018-03-22 7:16 ` 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=834ll8k1tx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30800@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--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).