From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Menu-bar flickering on Win10
Date: Wed, 02 Nov 2022 15:53:10 +0200 [thread overview]
Message-ID: <83o7tpa2ex.fsf@gnu.org> (raw)
In-Reply-To: <86cza57a3s.fsf@gnu.org> (message from Arash Esbati on Wed, 02 Nov 2022 14:35:19 +0100)
> From: Arash Esbati <arash@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 02 Nov 2022 14:35:19 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Does the code involved in the display of completion temporarily
> > switches to a different window, or changes the major mode?
>
> No, it is in a single window and the only buffer I used.
Didn't you say child frames are involved? If so, there are at least 2
frames, and each frame has at least one window. Right?
> > IOW, I suggest to step through the code which is involved, and see
> > which part of it actually causes the flickering. There's too many
> > unknowns in what you described.
>
> I did only this:
I didn't mean to say you are responsible in some way. I meant to say
that we need to understand better what code causes the flickering.
And the only way I could think of was to step through the code which
displays the completion candidates, because that's where the
flickering happens.
> My first reaction was if corfu is probably the problem since it uses
> child frames and not overlays, hence my question.
Could be. I simply don't know yet. Which is why I suggested to step
through the code.
next prev parent reply other threads:[~2022-11-02 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 12:08 Menu-bar flickering on Win10 Arash Esbati
2022-11-02 12:14 ` Po Lu
2022-11-02 13:17 ` Eli Zaretskii
2022-11-02 13:35 ` Arash Esbati
2022-11-02 13:53 ` Eli Zaretskii [this message]
2022-11-02 14:07 ` Arash Esbati
2022-11-02 15:11 ` Eli Zaretskii
2022-11-03 10:46 ` Arash Esbati
2022-11-03 11:26 ` Eli Zaretskii
2022-11-03 11:51 ` Po Lu
2022-11-03 13:55 ` Arash Esbati
-- strict thread matches above, loose matches on Subject: below --
2022-11-04 12:51 Johan Myréen
2022-11-04 13:54 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o7tpa2ex.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arash@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.