From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: cpitclaudel@gmail.com, 40857@debbugs.gnu.org
Subject: bug#40857: Invisibility specs do not apply to specified spaces
Date: Mon, 27 Apr 2020 18:20:03 +0300 [thread overview]
Message-ID: <83lfmh3qho.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBcwWaGJog7yVzueiUNz8x2+ZcjK=99Vz+519mkVe=PSrw@mail.gmail.com> (message from Pip Cet on Sun, 26 Apr 2020 19:01:29 +0000)
> From: Pip Cet <pipcet@gmail.com>
> Date: Sun, 26 Apr 2020 19:01:29 +0000
> Cc: Clément Pit-Claudel <cpitclaudel@gmail.com>,
> 40857@debbugs.gnu.org
>
> On Sun, Apr 26, 2020 at 3:22 PM Eli Zaretskii <eliz@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.
prev parent reply other threads:[~2020-04-27 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 23:18 bug#40857: Invisibility specs do not apply to specified spaces Clément Pit-Claudel
2020-04-26 15:20 ` Eli Zaretskii
2020-04-26 16:04 ` Clément Pit-Claudel
2020-04-26 17:01 ` Eli Zaretskii
2020-04-26 17:25 ` Clément Pit-Claudel
2020-04-26 17:45 ` Eli Zaretskii
2020-04-26 19:01 ` Pip Cet
2020-04-27 15:20 ` Eli Zaretskii [this message]
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=83lfmh3qho.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40857@debbugs.gnu.org \
--cc=cpitclaudel@gmail.com \
--cc=pipcet@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 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).