From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: RE: `looking-back' strange warning
Date: Fri, 2 Oct 2015 08:03:12 -0700 (PDT) [thread overview]
Message-ID: <6fe4b1c3-1557-426c-b599-da3fa8da5215@default> (raw)
In-Reply-To: <jwvio6po2ss.fsf-monnier+INBOX@gnu.org>
> > That's what a deprecation notice is for. It is not what
> > warnings are for. And certainly not a self-proclaimed
> > "warning" that incorrectly and nonsensically states that
> > "2-3" arguments are required when only 1 is required.
>
> I'm glad those little annoyances keep you entertained.
Please reread the Subject line. Someone else, not I, was
apparently annoyed or puzzled enough to ask what this
incomprehensible "warning" is all about.
It may be "little" to you, but it was important or confusing
enough for someone to ask here for help about it. That's not
something to belittle or sneer at.
But no one asked what the corresponding deprecation notice
means. That notice is clear enough.
If you feel that a byte-compiler message can also help
here, please consider just saying that not using LIMIT is
deprecated. That's all. (Just a suggestion.)
next prev parent reply other threads:[~2015-10-02 15:03 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 8:25 `looking-back' strange warning Andreas Röhler
2015-10-01 6:20 ` Michael Heerdegen
2015-10-01 6:25 ` Tassilo Horn
2015-10-01 6:50 ` Dmitry Gutov
2015-10-01 7:49 ` Andreas Röhler
2015-10-01 8:20 ` Tassilo Horn
2015-10-01 8:46 ` Andreas Röhler
2015-10-01 9:29 ` Tassilo Horn
2015-10-02 0:10 ` Stefan Monnier
2015-10-02 15:21 ` Tassilo Horn
2015-10-01 16:00 ` Drew Adams
2015-10-01 17:56 ` Dmitry Gutov
2015-10-01 18:24 ` Andreas Röhler
2015-10-01 18:59 ` Dmitry Gutov
2015-10-01 19:55 ` Andreas Röhler
2015-10-01 20:26 ` Dmitry Gutov
2015-10-02 0:15 ` Stefan Monnier
2015-10-02 1:18 ` Michael Heerdegen
2015-10-02 5:13 ` Drew Adams
2015-10-02 20:28 ` Drew Adams
2015-10-02 20:59 ` Tassilo Horn
2015-10-02 21:35 ` Drew Adams
2015-10-03 6:26 ` Tassilo Horn
2015-10-03 6:45 ` Andreas Röhler
2015-10-03 15:20 ` Drew Adams
2015-10-03 15:17 ` Drew Adams
2015-10-02 1:19 ` Michael Heerdegen
2015-10-02 5:12 ` Drew Adams
2015-10-02 6:16 ` Andreas Röhler
2015-10-02 6:36 ` Michael Heerdegen
2015-10-02 12:46 ` Stefan Monnier
2015-10-02 15:02 ` Drew Adams
2015-10-02 19:08 ` Tom Tromey
2015-10-02 19:33 ` Stefan Monnier
2015-10-03 18:11 ` Stefan Monnier
[not found] ` <mailman.176.1443721449.16064.help-gnu-emacs@gnu.org>
2015-10-01 18:50 ` Barry Margolin
[not found] ` <<barmar-D40496.14502501102015@88-209-239-213.giganet.hu>
2015-10-01 23:42 ` Drew Adams
2015-10-02 0:12 ` Stefan Monnier
2015-10-02 5:10 ` Drew Adams
2015-10-02 12:48 ` Stefan Monnier
2015-10-02 15:03 ` Drew Adams [this message]
2015-10-02 15:21 ` Stefan Monnier
2015-10-02 15:24 ` Drew Adams
2015-10-02 19:28 ` Stefan Monnier
2015-10-01 12:35 ` Artur Malabarba
[not found] <<560B9C7F.2060301@easy-emacs.de>
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=6fe4b1c3-1557-426c-b599-da3fa8da5215@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@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 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.