From: Eli Zaretskii <eliz@gnu.org>
To: Michal Nazarewicz <mina86@mina86.com>
Cc: 74876@debbugs.gnu.org
Subject: bug#74876: 31.0.50; Force fringe refresh / force-window-update not affecting fringes
Date: Wed, 01 Jan 2025 20:54:37 +0200 [thread overview]
Message-ID: <86pll6l5zm.fsf@gnu.org> (raw)
In-Reply-To: <lx7bxza3slxr6xtx3zofnal4@mina86.com> (message from Michal Nazarewicz on Wed, 01 Jan 2025 19:14:40 +0100)
> From: Michal Nazarewicz <mina86@mina86.com>
> Cc: 74876@debbugs.gnu.org
> Date: Wed, 01 Jan 2025 19:14:40 +0100
>
> On Tue, Dec 17 2024, Eli Zaretskii wrote:
> > You have: declare this feature impossible to implement in a reasonable
> > way, given the restrictions of the current display engine design and
> > implementation.
> >
> > At the very least, I hope you will document this for the users, so
> > they are not surprised.
>
> pulse.el forces 10 refreshes every 30 ms. If that’s acceptable for
> package which is part of Emacs, a single refresh when people switch
> windows is good enough for a third-party package.
pulse.el typically refreshes only a small portion of a window, and
therefore redisplay will only redraw that portion. So this doesn't
normally lead to flickering (unless you pulse a large portion of the
window).
next prev parent reply other threads:[~2025-01-01 18:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 19:31 bug#74876: 31.0.50; Force fringe refresh / force-window-update not affecting fringes Michal Nazarewicz
2024-12-14 20:28 ` Eli Zaretskii
2024-12-14 21:39 ` Michal Nazarewicz
2024-12-15 7:06 ` Eli Zaretskii
2024-12-16 21:47 ` Michal Nazarewicz
2024-12-17 12:16 ` Eli Zaretskii
2024-12-17 13:20 ` Michal Nazarewicz
2024-12-17 14:19 ` Eli Zaretskii
2025-01-01 18:14 ` Michal Nazarewicz
2025-01-01 18:54 ` Eli Zaretskii [this message]
2025-01-01 19:02 ` Michal Nazarewicz
2025-01-01 19:39 ` 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=86pll6l5zm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74876@debbugs.gnu.org \
--cc=mina86@mina86.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 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.