From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 20253@debbugs.gnu.org, agrambot@gmail.com
Subject: bug#20253: 24.4; Document `region' face behavior changes, overlay, priority
Date: Mon, 12 Sep 2016 21:37:01 +0300 [thread overview]
Message-ID: <83wpih7ynm.fsf@gnu.org> (raw)
In-Reply-To: <ba530831-2ff4-49ed-9f21-b7373d55432a@default> (message from Drew Adams on Mon, 12 Sep 2016 10:19:42 -0700 (PDT))
> Date: Mon, 12 Sep 2016 10:19:42 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: drew.adams@oracle.com, 20253@debbugs.gnu.org
>
> I disagree that THIS is an "internal" and "obscure" feature, and
> that "it is not supposed to be used by Lisp programs that are not
> part of Emacs". It cannot be, if users want to control the behavior
> of the `region' overlay and similar.
Of course, you disagree: you filed the bug, didn't you?
> Questions about this arise from end users.
I didn't see any. Please invite those users to ask the questions here
or on emacs-devel. Maybe I will change my mind after hearing them.
> And the question of this bug report is not only about documenting
> (nil . NUMBER). It is about documenting the user-visible _behavior_
> change for region highlighting, and how to accommodate and control it.
I said nothing about that part.
next prev parent reply other threads:[~2016-09-12 18:37 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 [this message]
2016-09-21 18:11 ` Alex
2016-09-21 18:35 ` Eli Zaretskii
2016-09-21 19:10 ` Alex
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wpih7ynm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20253@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=drew.adams@oracle.com \
/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.