From: Drew Adams <drew.adams@oracle.com>
To: emacs-devel@gnu.org
Subject: Please reconsider removing the `defadvice' doc (ref: bug #16491)
Date: Sat, 9 Aug 2014 14:19:46 -0700 (PDT) [thread overview]
Message-ID: <73d938eb-a7cf-4b11-bf48-9d28696f49e4@default> (raw)
You want to push your replacement for `defadvice'. OK, that's
presumably all well and good. No doubt it is the best thing
since sliced bread (ou le fil a couper le beurre).
But it is a real disservice to users to have removed all of
the information about using `defadvice' from the Elisp manual.
I *really* hope you will reconsider this decision.
Lots of users write or maintain code that works across multiple
Emacs versions, including code that uses `defadvice'. Caring
about Emacs users means not throwing obstacles at them
unnecessarily. Making them hold onto Emacs 24.3 just to have
access to the `defadvice' doc is uncalled-for annoyance.
Such archaeological digging by users should not be necessary.
I can imagine some newbie developer having such a mindset, but
it is disappointing - and yes, shameful - that the leadership
of GNU Emacs has come to this.
At least please consider making this doc available as a
separate Info manual, if you insist on not letting users see
it in the Elisp manual. Call it "Stupid-Old-Defadvice Manual"
if you like. Discourage using `defadvice' anyway you like,
short of depriving users of information about it.
And no, "I kept the 60KB of docs in the Commentary section
of advice.el" is *not* an answer. You might as well have
said that you tossed 600 kilos of old literature in the
dumpster. "60 KB"! What an attitude!
And no, this is not about me. I keep multiple Emacs versions
anyway. It is only a relatively minor annoyance to have to
bring up an older version to get to this doc.
Not everyone who uses or wants to understand `defadvice' in
existing code will keep multiple Emacs versions, or will know
what version to backtrack to, to find this doc. And even a
minor annoyance imposed gratuitously on lots of users is
better avoided, especially for something as important and
complex as advising functions.
Bug #16491, with the same request to restore this doc, was
marked "done" back in January. Is "done" the new "wont-fix"?
According to NEWS, `defadvice' is not even deprecated. And
even if it were to become deprecated, it would presumably
- it should - continue to be supported for quite some time.
And documented.
next reply other threads:[~2014-08-09 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 21:19 Drew Adams [this message]
2014-08-09 21:49 ` Please reconsider removing the `defadvice' doc (ref: bug #16491) Stefan Monnier
2014-08-11 1:45 ` Richard Stallman
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=73d938eb-a7cf-4b11-bf48-9d28696f49e4@default \
--to=drew.adams@oracle.com \
--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.