From: Alex <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20253@debbugs.gnu.org
Subject: bug#20253: 24.4; Document `region' face behavior changes, overlay, priority
Date: Wed, 21 Sep 2016 13:10:43 -0600 [thread overview]
Message-ID: <87r38dnk5o.fsf@gmail.com> (raw)
In-Reply-To: <834m59f6ds.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 21 Sep 2016 21:35:27 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alex <agrambot@gmail.com>
>> Cc: Drew Adams <drew.adams@oracle.com>, 20253@debbugs.gnu.org
>> Date: Wed, 21 Sep 2016 12:11:08 -0600
>>
>> My curiosity about the meaning of a cons cell priority is what pushed me
>> to find and respond to this bug, so I guess that would count as one
>> question.
>>
>> Since the region overlay is a very common overlay, I think it is
>> important enough to at least have a passing statement about its priority
>> value type in the documentation. Even something like "For example, some
>> overlays use a cons cell priority (PRIMARY . SECONDARY), where SECONDARY
>> is used as a tie-breaker if the PRIMARY priorities and boundaries of the
>> overlays are equal." would be nice.
>
> I hoped to hear some practical reasons for this, not just curiosity.
> Like practical use cases where knowing that internal detail (as
> opposed to using the documented methods of comparing priorities etc.)
> is imperative for that use case.
I should have mentioned that aside from curiosity I did need to know
about what the region overlay's priority represented so that I can know
what priority to give overlays that interacted with the region overlay.
> People often ask questions here out of curiosity about the display
> engine's inner workings, for example, and I try to answer them as best
> as I can. But that doesn't mean all I write here in those discussions
> should be in the manual.
Right, but I think that the region overlay is prominent enough to have
all of its properties be in a documented form.
> IOW, the need to have some internal detail described in the manual
> (which implies we will have to update and maintain it for the years to
> come) should have more important reasons than just curiosity.
Hopefully the above is enough to warrant an extra sentence or two in the
manual.
next prev parent reply other threads:[~2016-09-21 19:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<0ad651bb-89bc-4e86-9354-063db1c400a2@default>
[not found] ` <<87inu2vx36.fsf@gmail.com>
[not found] ` <<83k2eh9ic9.fsf@gnu.org>
2016-09-12 17:19 ` bug#20253: 24.4; Document `region' face behavior changes, overlay, priority Drew Adams
2016-09-12 18:37 ` Eli Zaretskii
2016-09-21 18:11 ` Alex
2016-09-21 18:35 ` Eli Zaretskii
2016-09-21 19:10 ` Alex [this message]
2016-09-21 20:25 ` Drew Adams
2016-09-23 8:28 ` Eli Zaretskii
2019-10-12 19:02 ` Lars Ingebrigtsen
2015-04-03 21:02 Drew Adams
2016-09-11 23:24 ` Alex
2016-09-12 16:46 ` 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
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=87r38dnk5o.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=20253@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).