From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 72721@debbugs.gnu.org, gautier@gautierponsinet.xyz
Subject: bug#72721: 31.0.50; Visual-wrap-prefix-mode breaks Magit log buffers
Date: Thu, 22 Aug 2024 15:54:27 +0300 [thread overview]
Message-ID: <86plq0soos.fsf@gnu.org> (raw)
In-Reply-To: <378d3451-12b8-c802-4340-12e432bcaa35@gmail.com> (message from Jim Porter on Wed, 21 Aug 2024 12:12:00 -0700)
> Date: Wed, 21 Aug 2024 12:12:00 -0700
> From: Jim Porter <jporterbugs@gmail.com>
> Cc: 72721@debbugs.gnu.org, gautier@gautierponsinet.xyz
>
> ... and here's a new test case (overlay-min-width). This shows that now
> you can apply 'min-width' as an overlay property, which would be great
> for 'visual-wrap-prefix-mode'. I could then convert that code to use
> overlays (at least for 'min-width', maybe for 'wrap-prefix' too), which
> would make it easier to clean up when deactivating the mode.
Doesn't adding support for overlays boils down to replacing
Fget_text_property in get_display_property with Fget_char_property,
and otherwise keeping the code intact? display_min_width is the only
caller of get_display_property, so we can change that at will.
next prev parent reply other threads:[~2024-08-22 12:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 21:39 bug#72721: 31.0.50; Visual-wrap-prefix-mode breaks Magit log buffers Gautier Ponsinet
2024-08-20 0:46 ` Jim Porter
2024-08-20 11:53 ` Eli Zaretskii
2024-08-20 17:33 ` Jim Porter
2024-08-20 19:01 ` Eli Zaretskii
2024-08-21 3:15 ` Jim Porter
2024-08-21 5:18 ` Jim Porter
2024-08-21 19:12 ` Jim Porter
2024-08-22 12:54 ` Eli Zaretskii [this message]
2024-08-22 9:59 ` Eli Zaretskii
2024-08-22 9:53 ` Eli Zaretskii
2024-08-22 16:19 ` Jim Porter
2024-08-25 7:29 ` Eli Zaretskii
2024-08-25 16:26 ` Jim Porter
2024-08-25 17:39 ` Eli Zaretskii
2024-08-25 18:41 ` Jim Porter
2024-08-29 11:47 ` Eli Zaretskii
2024-08-30 5:01 ` Jim Porter
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=86plq0soos.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72721@debbugs.gnu.org \
--cc=gautier@gautierponsinet.xyz \
--cc=jporterbugs@gmail.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.