unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35508@debbugs.gnu.org
Subject: bug#35508: 27.0.50; Fine-ordering of functions on hooks
Date: Mon, 13 May 2019 09:29:36 -0400	[thread overview]
Message-ID: <jwv5zqebicp.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83tve1cd0d.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 11 May 2019 16:54:42 +0300")

>> >> Other objections?
>> > Thanks.  Should we perhaps change 100 to 110 and 90 to 100?
>> You mean make it go https://en.wikipedia.org/wiki/Up_to_eleven ?  ;-)
> Yes.  The idea is that 100 is easier to remember than either 90 or
> 110.

How 'bout 42, then?

More seriously: since I don't want `t` to be equivalent to the maximum
depth, there are 2 numbers to be "remembered".  In order to follow the
same convention as add-function, I'd really much prefer to keep 100 as
the maximum.  As for the value corresponding to `t`, I'm definitely not
wedded to 90, it could be any value in the ]0,100[ interval.
66?  50?  10?  99?  π?

>> Also I think it's important to use the same convention as for add-function.
> We can always document that in comments.

Will do.

> We could have checkdoc complain about values we don't want to see in
> application code.

I think that'd be more trouble than it's worth.
But I'll warn against using 100 (or -100), in the doc.


        Stefan





  reply	other threads:[~2019-05-13 13:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 20:37 bug#35508: 27.0.50; Fine-ordering of functions on hooks Stefan Monnier
2019-04-30 21:37 ` Drew Adams
2019-04-30 22:31   ` Stefan Monnier
2019-05-01 18:00 ` Eli Zaretskii
2019-05-01 20:29   ` Stefan Monnier
2019-05-08 18:32     ` Stefan Monnier
2019-05-11 12:05       ` Eli Zaretskii
2019-05-11 13:26         ` Stefan Monnier
2019-05-11 13:54           ` Eli Zaretskii
2019-05-13 13:29             ` Stefan Monnier [this message]
2019-05-29 19:56               ` Stefan Monnier

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=jwv5zqebicp.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=35508@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).