From: Clemens <clemens.radermacher@posteo.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46177@debbugs.gnu.org
Subject: bug#46177: 27.1; Display problem with minibuffer overlay when using display property
Date: Sat, 30 Jan 2021 10:30:21 +0100 [thread overview]
Message-ID: <f227a010-ae40-2ea3-fd69-4082af1476e1@posteo.de> (raw)
In-Reply-To: <83czxmakzc.fsf@gnu.org>
> Better in what sense?
>
> If you mean a way that prevents the background of the prompt from
> being applied to the text you display via the overlay, I think the
> best/only way is for the overlay string or display string to specify
> the background color.
Yes, I meant to avoid the issue that the minibuffer prompt face gets
applied to strings defined in the display property. The code I posted
simply removes any strings in the display spec and inlines them, which
seems to work well, too. The problem is not only the background color it
seems, I would need to completely undo the effects of the minibuffer
prompt face and I don't know how to do that. But what I'm doing now
works and if there isn't a better solution I'm fine with using it.
I don't understand the reasons for the current behaviour but please
check out the following which seems not appropriate to me:
(set-face-attribute 'minibuffer-prompt nil :foreground "purple")
(minibuffer-with-setup-hook
(lambda ()
(overlay-put
(make-overlay (point-max) (point-max) nil t t)
'after-string
(concat " from"
(propertize " world"
'display
" minibuffer"))))
(read-string "Hello"))
Even with the " from" string between the string defined in the display
property gets the prompt face applied.
next prev parent reply other threads:[~2021-01-30 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 17:58 bug#46177: 27.1; Display problem with minibuffer overlay when using display property Clemens
2021-01-29 18:37 ` Eli Zaretskii
2021-01-29 20:26 ` Clemens
2021-01-30 8:26 ` Eli Zaretskii
2021-01-30 9:30 ` Clemens [this message]
2021-01-30 10:46 ` Eli Zaretskii
2021-01-30 11:09 ` Clemens
2021-01-30 12:06 ` Eli Zaretskii
2021-01-30 12:10 ` Clemens
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=f227a010-ae40-2ea3-fd69-4082af1476e1@posteo.de \
--to=clemens.radermacher@posteo.de \
--cc=46177@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.