GNU bug report logs - #40857
Invisibility specs do not apply to specified spaces

Previous Next

Package: emacs;

Reported by: Clément Pit-Claudel <cpitclaudel <at> gmail.com>

Date: Sat, 25 Apr 2020 23:19:02 UTC

Severity: wishlist

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pip Cet <pipcet <at> gmail.com>
Cc: cpitclaudel <at> gmail.com, 40857 <at> debbugs.gnu.org
Subject: bug#40857: Invisibility specs do not apply to specified spaces
Date: Mon, 27 Apr 2020 18:20:03 +0300
> From: Pip Cet <pipcet <at> gmail.com>
> Date: Sun, 26 Apr 2020 19:01:29 +0000
> Cc: Clément Pit-Claudel <cpitclaudel <at> gmail.com>, 
> 	40857 <at> debbugs.gnu.org
> 
> On Sun, Apr 26, 2020 at 3:22 PM Eli Zaretskii <eliz <at> gnu.org> wrote:
> > I don't think this is a bug.  A "replacing" display property in effect
> > forces the display engine to ignore the entire chunk of text "covered"
> > by that display property,
> 
> That's only true for text properties: a display property on an empty
> overlay is ignored.

Can you show a Lisp snippet for that?  I don't think I have a clear
idea of the use case.

> The right fix, I think, is to apply the patch in bug#40845, possibly
> extending it to pass in an "invisible" flag to the Lisp code that
> calculates the actual display spec to be used.

I explained elsewhere why I think we shouldn't move display
functionalities to Lisp, except as the last resort, more or less.




This bug report was last modified 5 years and 53 days ago.

Previous Next


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