GNU bug report logs - #73600
31.0.50; Visual wrap prefix mode and image display

Previous Next

Full log

Message #44 received at 73600 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jim Porter <jporterbugs <at> gmail.com>
Cc: 73600 <at> debbugs.gnu.org, gautier <at> gautierponsinet.xyz
Subject: Re: bug#73600: 31.0.50; Visual wrap prefix mode and image display
Date: Sun, 13 Oct 2024 08:36:01 +0300

> Date: Sat, 12 Oct 2024 18:36:27 -0700
> Cc: 73600 <at> debbugs.gnu.org, gautier <at> gautierponsinet.xyz
> From: Jim Porter <jporterbugs <at> gmail.com>
> 
> +    ;; Check if the display property at the end of this line is "safe".
> +    (if (visual-wrap--display-property-safe-p
> +         (get-char-property (pos-eol) 'display))
> +        ;; If so, we can apply our visual wrapping properties to this
> +        ;; line and continue to the next line.
> +        (progn
> +          (visual-wrap--apply-to-line (point))
> +          (forward-line))
> +      ;; Otherwise, skip ahead to the beginning of the first line after
> +      ;; the unsafe display property changes.
> +      (goto-char (next-single-char-property-change (pos-eol) 'display))

Yes, this is what I had in mind, thanks.  But does
next-single-char-property-change really fit the bill?  What if you
have several overlapping 'display' properties, and in particular one
property "enclosed" in another?  Did you test such a scenario?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.