unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Tue, 17 Dec 2024 14:20:52 +0100	[thread overview]
Message-ID: <71m50+9qm4uxqup7x3scw9xa@mina86.com> (raw)
In-Reply-To: <8634impkrb.fsf@gnu.org>

On Tue, Dec 17 2024, Eli Zaretskii wrote:
>> From: Michal Nazarewicz <mina86@mina86.com>
>> Cc: 74876@debbugs.gnu.org
>> Date: Mon, 16 Dec 2024 22:47:43 +0100
>> 
>> On Sun, Dec 15 2024, Eli Zaretskii wrote:
>> > Thanks.  I don't think what you want can possibly work, unless we
>> > completely redesign how the fringes are updated.
>> 
>> Well… there’s always the atomic option of calling redraw-frame.  Though
>> I’ve found that changing an attribute of a font is sufficient.
>> I believe what makes things work is setting f->face_change and calling
>> fset_redisplay.
>
> Both methods are quite expensive, and will cause flickering in some
> configurations,

Yes, I’ve figured as much, but it’s not like I have another choice.

auto-dim-other-buffers redraws entire windows already; someone using
likely has setup that can handle full frame redraws as well.

-- 
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»





  reply	other threads:[~2024-12-17 13:20 UTC|newest]

Thread overview: 8+ 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 [this message]
2024-12-17 14:19             ` 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=71m50+9qm4uxqup7x3scw9xa@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).