From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: Nested display strings
Date: Sun, 24 Apr 2011 01:16:13 +0300 [thread overview]
Message-ID: <83d3kcbolu.fsf@gnu.org> (raw)
In-Reply-To: <14612DC1D0654DA6898D782225821BEC@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Sat, 23 Apr 2011 13:31:47 -0700
>
> Don't `display' and `priority' get along well, or can't they be be made to get
> along?
>
> We have two overlapping overlays here, and the usual way to determine what
> happens when overlays overlap is by looking at their `priority' values (among
> other things).
In the example that started this thread, there were no priorities at
all. The question is, whether the behavior in that case is correct or
not.
But even if different priorities were involved, how do they help
resolve the issue with overlays that have `display' property whose
value is a string or an image? These overlay properties _replace_ the
buffer text, not determine how to display the buffer text. If the two
overlays were covering the same range of buffer positions, then we
could expect that the overlay with the higher priority would "win".
But what to do in the case I presented, where one of the overlays
covers only a subset of positions covered by the other? How can
priorities help in that case? If the "shorter" overlay has a higher
priority, what to display instead of the characters covered only by
the "longer" one? Either nothing or you get the duplicate display of
STRING1 again. Both alternatives look bad.
> If `display' and `priority' can be made to cooperate then that would be good.
I don't see how could they; see above.
next prev parent reply other threads:[~2011-04-23 22:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 16:44 Nested display strings Eli Zaretskii
2011-04-23 19:42 ` Andreas Röhler
2011-04-23 20:07 ` Eli Zaretskii
2011-04-23 20:31 ` Drew Adams
2011-04-23 22:16 ` Eli Zaretskii [this message]
2011-04-23 23:20 ` Drew Adams
2011-04-24 6:25 ` Eli Zaretskii
2011-04-24 5:01 ` Stefan Monnier
2011-04-24 17:37 ` Eli Zaretskii
2011-04-25 12:47 ` Stefan Monnier
2011-04-25 13:29 ` Eli Zaretskii
2011-04-25 14:57 ` Stefan Monnier
2011-04-25 19:03 ` Juanma Barranquero
2011-04-25 19:41 ` Chong Yidong
2011-04-25 19:56 ` Eli Zaretskii
2011-04-26 18:04 ` Chong Yidong
2011-04-26 18:28 ` Eli Zaretskii
2011-04-26 12:53 ` Stefan Monnier
2011-04-26 17:51 ` Eli Zaretskii
2011-04-26 18:13 ` Ted Zlatanov
2011-04-26 18:25 ` Eli Zaretskii
2011-04-26 18:35 ` chad
2011-04-26 18:50 ` Ted Zlatanov
2011-04-26 19:19 ` Drew Adams
2011-04-28 0:45 ` Stefan Monnier
2011-04-28 16:48 ` Eli Zaretskii
2011-04-28 18:42 ` Stefan Monnier
2011-04-26 20:51 ` Chong Yidong
2011-04-27 0:59 ` Stefan Monnier
2011-04-26 14:46 ` Richard Stallman
2011-04-24 5:19 ` Michael Welsh Duggan
2011-04-24 6:17 ` Eli Zaretskii
2011-04-24 6:22 ` Michael Welsh Duggan
2011-04-24 6:31 ` Andreas Röhler
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=83d3kcbolu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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.