all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sora Takai <booksipadtest@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: About the interpretation of negative integer values for 'priority overlay property
Date: Mon, 19 Feb 2024 22:06:38 +0900	[thread overview]
Message-ID: <CADWbB7CKekvnE7MBc5hiLPp4FRpVuixLz-m8fwKo8aw3i1LgDw@mail.gmail.com> (raw)
In-Reply-To: <86zfvwprfz.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

Got it - thanks for clarifying!

-Sora

On Mon, Feb 19, 2024 at 9:30 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Sora Takai <booksipadtest@gmail.com>
> > Date: Mon, 19 Feb 2024 11:10:42 +0900
> >
> > 1. Are negative 'priority integers interpreted in an intuitive sense?
> That is, would overlays with negative
> > 'priority numbers rank distinctly lower than anything with higher
> 'priority values (0 or above)?
> >
> > 2. Are they "valid" in a sense that emacs intends 'priority property to
> be (in which case the manual description
> > would have to be changed).
>
> Negative priority values are valid, but used internally by Emacs.  So
> we don't recommend using them in Lisp programs, as doing so might get
> in the way of some Emacs features.
>
> > Personally, I think having negative 'priority -- given it works as
> intended -- is useful, since I sometimes bump
> > into use cases where I'd like to make sure certain overlays have the
> lowest 'priority possible below all others.
>
> We recommend you not to use these values.
>

[-- Attachment #2: Type: text/html, Size: 1528 bytes --]

      reply	other threads:[~2024-02-19 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  2:10 About the interpretation of negative integer values for 'priority overlay property Sora Takai
2024-02-19 12:30 ` Eli Zaretskii
2024-02-19 13:06   ` Sora Takai [this message]

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=CADWbB7CKekvnE7MBc5hiLPp4FRpVuixLz-m8fwKo8aw3i1LgDw@mail.gmail.com \
    --to=booksipadtest@gmail.com \
    --cc=eliz@gnu.org \
    --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.