From: Stefan Kangas <stefan@marxist.se>
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: Thu, 3 Oct 2019 02:20:07 +0200 [thread overview]
Message-ID: <CADwFkmnD4Yv=+AR+bFLi0XqnqX_9qGWxCnY_iLx-2uEw3WvFuA@mail.gmail.com> (raw)
In-Reply-To: <CAOqdjBfbP4DsSnR9Zj92xJqB1LQyw5ehHK+JK94OYjRt5wCvGQ@mail.gmail.com>
Pip Cet <pipcet@gmail.com> writes:
> On Mon, Nov 19, 2018 at 7:37 PM Eli Zaretskii <eliz@gnu.org> wrote:
>> > This is a feature request: I'd like to be able to display an empty line
>> > as a non-empty line with images in it.
>>
>> I don't think I understand this. Can you elaborate what that means?
>>
>> 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.
>
> 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.
Is this feature request still relevant, or did Eli's reply solve this
use case? Thanks.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-10-03 0:20 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
2019-10-03 0:20 ` Stefan Kangas [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmnD4Yv=+AR+bFLi0XqnqX_9qGWxCnY_iLx-2uEw3WvFuA@mail.gmail.com' \
--to=stefan@marxist.se \
--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 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.