From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: RE: How can I remove effects of text properties in 'before-string
Date: Sun, 22 Oct 2017 10:32:20 -0700 (PDT) [thread overview]
Message-ID: <f95efc2a-3d08-4262-b704-43462cc79208@default> (raw)
In-Reply-To: <<837evnazze.fsf@gnu.org>>
> > Is this behavior documented? I couldn't find anything
> > about it, but it might well be there somewhere. I looked
> > in the doc about overlays and the doc about the margin,
> > but perhaps it is there and I overlooked or misread it.
>
> It's indirectly documented in "Displaying Faces".
OK. The margin-spec `display' property is applied in
this case to a zero-length buffer zone. And a margin-spec
`display' property is of type "replacing", so the text
in that zone is not shown (which has no effect, since
the zone is empty).
What you say makes sense: face `hl-line-face' is used
for an overlay that covers the empty zone in question,
so that face is active there, so it is visible for the
margin-spec `display' overlay.
Still, I don't think this behavior is obvious, from
the doc. I'm not sure where it should be pointed out,
but I think it would help to do so, even if it does
follow from what is written now.
Perhaps point this out explicitly in node `Displaying
Faces'. And perhaps xref that node from node `Display
Margins', since a margin spec is a likely gotcha candidate).
> Not a bug: the code does this on purpose, and even has comments that
> explicitly describe this. Emacs worked like that since v21.1.
Code comments are one way to make the design and behavior
clear. The Elisp manual is another way - a better way to
get across something like this to most users.
Thank you for the explanation. Please consider improving
the doc to make this behavior clearer.
next prev parent reply other threads:[~2017-10-22 17:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<87tvyrabkk.fsf@gmail.com>
[not found] ` <<838tg3b27v.fsf@gnu.org>
2017-10-22 16:33 ` How can I remove effects of text properties in 'before-string Drew Adams
2017-10-22 16:50 ` Eli Zaretskii
[not found] ` <<837evnazze.fsf@gnu.org>
2017-10-22 17:32 ` Drew Adams [this message]
2017-10-27 14:44 ` Eli Zaretskii
2017-10-22 7:25 Amos Bird
2017-10-22 7:43 ` Amos Bird
2017-10-22 16:00 ` Emanuel Berg
2017-10-22 17:07 ` Amos Bird
2017-10-22 16:02 ` Eli Zaretskii
2017-10-22 17:07 ` Amos Bird
2017-10-22 17:15 ` Eli Zaretskii
2017-10-22 18:08 ` Amos Bird
2017-10-22 18:24 ` Eli Zaretskii
2017-10-22 19:12 ` Amos Bird
2017-10-22 19:34 ` Eli Zaretskii
2017-10-23 12:57 ` Stefan Monnier
[not found] <<<87tvyrabkk.fsf@gmail.com>
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=f95efc2a-3d08-4262-b704-43462cc79208@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).