From: "Clément Pit--Claudel" <clement.pitclaudel@live.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25592@debbugs.gnu.org
Subject: bug#25592: Feature request: sorting overlays
Date: Tue, 7 Feb 2017 14:17:13 -0500 [thread overview]
Message-ID: <63b6a300-4892-260a-2054-c922485ee192@live.com> (raw)
In-Reply-To: <83mvdx6i0s.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1247 bytes --]
On 2017-02-07 12:13, Eli Zaretskii wrote:
>> Cc: 25592@debbugs.gnu.org
>> From: Clément Pit--Claudel <clement.pitclaudel@live.com>
>> Date: Sun, 5 Feb 2017 14:51:55 -0500
>>
>>>>> What will happen if you have 2 overlays like this:
>>>>>
>>>>> +------------- OV2 -------+
>>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>> +------- OV1 ---------+
>>>>>
>>>>> and OV2 has a higher priority than OV1?
>>>>
>>>> The two overlays get sorted as (OV1 OV2).
>>>
>>> But OV2 has a higher priority, so it should be the first in the sorted
>>> order, no?
>>
>> I process them in order of increasing priority, so OV1 gets processed first.
>
> So you actually apply _all_ of the overlays in the buffer, one by one?
> That's really inefficient. With my proposal, you'd only need to apply
> at most one overlay at each position where some overlay begins or
> ends, and do that for much fewer text segments.
I think I may have misunderstood your proposal, or failed to express what I was trying to achieve :/ If OV1 has face "(:weight bold)" and OV2 has face "(:slant italic)", I want to save both 'face properties. Can I really do that by applying at most one overlay at each position?
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-02-07 19:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 20:32 bug#25592: Feature request: sorting overlays Clément Pit--Claudel
2017-02-01 13:01 ` Eli Zaretskii
2017-02-02 19:41 ` Clément Pit--Claudel
2017-02-02 20:43 ` Eli Zaretskii
2017-02-03 15:19 ` Clément Pit--Claudel
2017-02-03 21:17 ` Eli Zaretskii
2017-02-03 21:51 ` Clément Pit--Claudel
2017-02-04 8:13 ` Eli Zaretskii
2017-02-05 16:21 ` Clément Pit--Claudel
2017-02-05 18:28 ` Eli Zaretskii
2017-02-05 19:10 ` Clément Pit--Claudel
2017-02-05 19:43 ` Eli Zaretskii
2017-02-05 19:51 ` Clément Pit--Claudel
2017-02-07 17:13 ` Eli Zaretskii
2017-02-07 19:17 ` Clément Pit--Claudel [this message]
2017-02-07 19:56 ` Eli Zaretskii
2017-02-07 20:07 ` Clément Pit--Claudel
2017-02-08 17:22 ` Eli Zaretskii
2017-02-09 19:50 ` Clément Pit--Claudel
2017-02-03 23:28 ` Johan Bockgård
2017-02-04 8:29 ` Eli Zaretskii
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=63b6a300-4892-260a-2054-c922485ee192@live.com \
--to=clement.pitclaudel@live.com \
--cc=25592@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.