From: Travis Foster <tsfoster@mtu.edu>
To: Drew Adams <drew.adams@oracle.com>, 25348@debbugs.gnu.org
Subject: bug#25348: `display` property faces are prioritized above overlays
Date: Tue, 3 Jan 2017 14:52:26 -0800 [thread overview]
Message-ID: <CADS09+CkaiN=5dNCn36Hnz4XUX3_GCpzf0TnobBeUKPUBjbgHA@mail.gmail.com> (raw)
In-Reply-To: <3385c032-ead0-4890-8cf4-e54375ea8ac7@default>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
Yes, the text in the buffer is replaced by its display text, with the face.
Then, I would expect the overlay to apply to all the text on the line,
including the replacement text. Since the properties in overlays are
supposed to take priority over the properties in the buffer itself, I don't
think it makes sense for the replacement to take priority over the
overlay. Is that wrong? It seems that the replacement should occur, and
then the resulting text should be modified further by the overlay.
On Tue, Jan 3, 2017 at 2:29 PM, Drew Adams <drew.adams@oracle.com> wrote:
> > When I do the following (for example):
> > (put-text-property (point) (1+ (point))
> > 'display (propertize "." 'face 'header-line))
> ...
> > But it seems like in this case, the display text property
> > is taking priority over the the overlay.
>
> You are using a "replacing" `display'-property spec.
> See (elisp) `Replacing Specs'.
> http://www.gnu.org/software/emacs/manual/html_node/elisp/
> Replacing-Specs.html
>
> Your text that has the property is entirely replaced (for display)
> by what is specified for property `display'.
>
[-- Attachment #2: Type: text/html, Size: 1677 bytes --]
next prev parent reply other threads:[~2017-01-03 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 22:17 bug#25348: `display` property faces are prioritized above overlays Travis Foster
2017-01-03 22:29 ` Drew Adams
2017-01-03 22:52 ` Travis Foster [this message]
2017-01-04 16:06 ` Eli Zaretskii
2017-01-04 19:25 ` Travis Foster
2017-01-04 19:55 ` Eli Zaretskii
2017-01-04 21:59 ` Travis Foster
2017-01-05 16:27 ` Eli Zaretskii
2017-01-05 18:10 ` Travis Foster
2019-09-29 16:22 ` Lars Ingebrigtsen
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='CADS09+CkaiN=5dNCn36Hnz4XUX3_GCpzf0TnobBeUKPUBjbgHA@mail.gmail.com' \
--to=tsfoster@mtu.edu \
--cc=25348@debbugs.gnu.org \
--cc=drew.adams@oracle.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.