From: "João Távora" <joaotavora@gmail.com>
To: 28390@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#28390: Fwd: bug#28390: 26.0.50; overlays-at actually sorts by increating priority
Date: Fri, 8 Sep 2017 20:30:46 +0100 [thread overview]
Message-ID: <CALDnm5083TSfQLODfaaTD5n2enKUBnCV_FF06dwrYHa3jO-gmw@mail.gmail.com> (raw)
In-Reply-To: <CALDnm5103cjV6TNKiGiaVEcJRLMfnM+wCuW3LrySh8dEur7uwg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
---------- Forwarded message ----------
From: João Távora <joaotavora@gmail.com>
Date: Fri, Sep 8, 2017 at 7:48 PM
Subject: Re: bug#28390: 26.0.50; overlays-at actually sorts by increating
priority
To: Eli Zaretskii <eliz@gnu.org>
On Fri, Sep 8, 2017 at 10:47 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > Really? Won't that ripple very paintuflly across the elisp ecosphere?
>
> I don't think so. I believe this optional argument is used very
> rarely.
>
> > I do agree that it should sort the other way, though. But it's too late
> > for that, bugs will be features :-).
>
> I'm not sure it's too late.
You might be right. Even I overestimated how much I use it in my libs. I
don't.
And the few first pages of a github code search for overlays-at don't
disprove
you. But they don't prove anything either.
Anyway, your call. I wouldn't do it, what's to gain besides consistency?
--
João Távora
[-- Attachment #2: Type: text/html, Size: 1785 bytes --]
next prev parent reply other threads:[~2017-09-08 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 22:21 bug#28390: 26.0.50; overlays-at actually sorts by increating priority João Távora
2017-09-08 8:39 ` Eli Zaretskii
2017-09-08 8:57 ` João Távora
2017-09-08 9:47 ` Eli Zaretskii
[not found] ` <CALDnm5103cjV6TNKiGiaVEcJRLMfnM+wCuW3LrySh8dEur7uwg@mail.gmail.com>
2017-09-08 19:30 ` João Távora [this message]
2017-09-10 13:53 ` Stefan Monnier
2017-09-16 10:04 ` 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=CALDnm5083TSfQLODfaaTD5n2enKUBnCV_FF06dwrYHa3jO-gmw@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=28390@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).