From: Michal Nazarewicz <mina86@mina86.com>
To: Eli Zaretskii <eliz@gnu.org>
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:02:45 +0100 [thread overview]
Message-ID: <7okn4mf143680yga1fqtbdbf@mina86.com> (raw)
In-Reply-To: <86pll6l5zm.fsf@gnu.org>
On Wed, Jan 01 2025, Eli Zaretskii wrote:
>> 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).
pulse.el changes face which forces refresh just as I described in this
thread. If you’re saying Emacs is smart enough to notice that only
small portion of the window needs refreshing, this should also be true
in my case where only fringes need refreshing.
--
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»
next prev parent reply other threads:[~2025-01-01 19:02 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
2025-01-01 19:02 ` Michal Nazarewicz [this message]
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
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=7okn4mf143680yga1fqtbdbf@mina86.com \
--to=mina86@mina86.com \
--cc=74876@debbugs.gnu.org \
--cc=eliz@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 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).