From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 33435@debbugs.gnu.org
Subject: bug#33435: 27.0.50; A use case for recursive display specifications
Date: Tue, 20 Nov 2018 18:30:06 +0200 [thread overview]
Message-ID: <83o9ajiuep.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBeJ9fWffxJGJFaG0j3PnAMt2U_7T2r0BLRCY6-9=x6n3g@mail.gmail.com> (message from Pip Cet on Tue, 20 Nov 2018 15:16:25 +0000)
> From: Pip Cet <pipcet@gmail.com>
> Date: Tue, 20 Nov 2018 15:16:25 +0000
> Cc: 33435@debbugs.gnu.org
>
> > In case I did understand: did you try an overlay with after-string
> > that has an image display property on it?
>
> First, thanks for the suggestion; sorry, it simply hadn't occurred to
> me that after/before-string can do things display specifications
> cannot.
Well, it's still a display spec, just on a string, not on buffer text.
> Obviously I'm still thinking of a display-propertized display
> specification string as the more natural thing to do, and things are
> slightly different (cursor placement, modifications, highlighting of
> included text) with the after-string solution, but I'll try to get
> things working that way. Thanks again.
Let me know if you have other difficulties. I should warn you that
the combination of an overlay string and a display spec is used
rarely, so you might bump into weird behavior and even bugs. Until
Emacs 25 I think this combination was very buggy.
next prev parent reply other threads:[~2018-11-20 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 18:51 bug#33435: 27.0.50; A use case for recursive display specifications Pip Cet
2018-11-19 19:37 ` Eli Zaretskii
2018-11-20 15:16 ` Pip Cet
2018-11-20 16:30 ` Eli Zaretskii [this message]
2019-10-03 0:20 ` Stefan Kangas
2019-10-03 12:33 ` Pip Cet
2019-10-03 16:42 ` Stefan Kangas
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=83o9ajiuep.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33435@debbugs.gnu.org \
--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).