unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex <agrambot@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 20253@debbugs.gnu.org
Subject: bug#20253: 24.4; Document `region' face behavior changes, overlay, priority
Date: Sun, 11 Sep 2016 17:24:45 -0600	[thread overview]
Message-ID: <87inu2vx36.fsf@gmail.com> (raw)
In-Reply-To: <0ad651bb-89bc-4e86-9354-063db1c400a2@default> (Drew Adams's message of "Fri, 3 Apr 2015 14:02:26 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> Since Emacs 24.3, if I recall correctly, face `region' uses an overlay.
> This produces changes in the user-observable behavior - that's why the
> change was made.
>
> But the NEWS for 24.3 and for 24.4 do not mention anything about this,
> AFAICT.  Not only does NEWS not seem to say anything about `region'
> using an overlay, but it does not even mention the observable behavior
> differences that this produces.
>
> And the Elisp manual is likewise silent on this change.
>
> Please tell users that such a change was made.  That's what NEWS is for.
>
> And please tell users, in the Elisp manual, what the default priority of
> the overlay is.  Testing shows a priority value of (nil . 100), which is
> not even a documented form that an overlay priority can take.  But even
> if that is what the value needs to be, for internal reasons, at least
> tell users what it is.
>
> And if, for some reason, users are supposed not to change the priority,
> then say so, in the doc.  And if there is no such restriction or
> recommendation, then let them know, if they should be assigning a
> priority value that is a cons, such as (nil . NUMBER).
>
> IOW, please communicate with your users about such changes: what they
> mean for users (what behavior differences they can expect), and how they
> can manipulate/customize the behavior.

The Elisp manual does mention that "Emacs sometimes uses non-numeric
priority values for some of its internal overlays", but it would be nice
if it documented what those were and what they mean.

The comments in simple.el mention that a cons cell value represents
primary/secondary priorities, but it's not clear what the difference is.





  reply	other threads:[~2016-09-11 23:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 21:02 bug#20253: 24.4; Document `region' face behavior changes, overlay, priority Drew Adams
2016-09-11 23:24 ` Alex [this message]
2016-09-12 16:46   ` Eli Zaretskii
     [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     ` 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
2016-09-21 20:25               ` Drew Adams
2016-09-23  8:28               ` Eli Zaretskii
2019-10-12 19:02                 ` 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

  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=87inu2vx36.fsf@gmail.com \
    --to=agrambot@gmail.com \
    --cc=20253@debbugs.gnu.org \
    --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 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).