From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 20592@debbugs.gnu.org, haroogan@gmail.com
Subject: bug#20592: the `display' property messes the `face' properties after `concat'
Date: Tue, 19 May 2015 18:31:23 +0300 [thread overview]
Message-ID: <83fv6seg8k.fsf@gnu.org> (raw)
In-Reply-To: <jwvh9r9pdnq.fsf-monnier+emacsbugs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Alexander Shukaev <haroogan@gmail.com>, 20592@debbugs.gnu.org
> Date: Mon, 18 May 2015 21:20:05 -0400
>
> > The behavior you observe is because the ':eval' construct expects to
> > produce a single string with either the same common face spec on all
> > of its characters, or no faces at all. You cannot use ':eval' to
> > produce a string that has more than one face spec on its different
> > characters; if you do, only the face spec of the first character of
> > the string will be honored.
>
> IIUC, this is the bug that needs to be fixed.
> Or is there a reason to consider this as a feature?
I think the reason for this implementation was to keep the code simple
and efficient. After all, ':eval' is part of the standard mode line,
in several places, so this code runs each time we update the mode
line, which we do a lot.
I agree that the limitation is counter-intuitive, and barely
documented, but given that using a separate ':eval' is such an easy
solution, perhaps we should simply document this. Fixing this doesn't
sound as high priority to me.
next prev parent reply other threads:[~2015-05-19 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 23:58 bug#20592: the `display' property messes the `face' properties after `concat' Alexander Shukaev
2015-05-17 14:39 ` Eli Zaretskii
2015-05-19 1:20 ` Stefan Monnier
2015-05-19 15:31 ` Eli Zaretskii [this message]
2015-06-25 19:16 ` Alexander Shukaev
2015-06-25 19:42 ` Eli Zaretskii
2021-12-02 10:00 ` 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=83fv6seg8k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20592@debbugs.gnu.org \
--cc=haroogan@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.