From: Drew Adams <drew.adams@oracle.com>
To: 16491@debbugs.gnu.org
Subject: bug#16491: 24.3.50; REGRESSION: `defadvice' doc removed from Elisp manual
Date: Sat, 18 Jan 2014 22:45:09 -0800 (PST) [thread overview]
Message-ID: <b1393b6a-e597-427e-a7c5-ca309ee6dbc0@default> (raw)
Elisp manual node `Advising Emacs Lisp Functions' has been rewritten to
include the new `add-function' stuff. It is fine to document that new
feature.
What's not fine is to simply remove all of the doc about the traditional
`defadvice' advice system. Even if that feature is to be deprecated,
its doc should remain until it is desupported. If this removal is not
a temporary oversight (mistake) then it is quite misguided. It hurts
Emacs users.
The Elisp manual should continue to be usable to help users code
`defadvice' advice, in addition to `add-function' advice. As one use
case, some users will use Emacs 24.4 to write or maintain code for
older or multiple Emacs versions.
Normally there is a reasonably long transition period before a feature,
especially a major feature such as `defadvice', is desupported. And
until desupport, the deprecated feature remains SUPPORTED - in
particular, by continuing to provide users with its reference doc.
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2014-01-17 on ODIEONE
Bzr revision: 116059 michael.albinus@gmx.de-20140117182409-gz695p2c951idlee
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
CPPFLAGS=-Ic:/Devel/emacs/include'
next reply other threads:[~2014-01-19 6:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12294.1390113984.10748.bug-gnu-emacs@gnu.org>
2014-01-19 6:45 ` Drew Adams [this message]
2014-01-19 16:58 ` bug#16491: 24.3.50; ?REGRESSION: `defadvice' doc removed from Elisp manual Alan Mackenzie
2014-01-19 20:40 ` Stefan Monnier
2014-01-19 22:32 ` Drew Adams
2014-01-20 2:31 ` Stefan Monnier
2014-01-22 22:11 ` Alan Mackenzie
2014-01-22 22:20 ` Daniel Colascione
2014-01-22 22:42 ` Drew Adams
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=b1393b6a-e597-427e-a7c5-ca309ee6dbc0@default \
--to=drew.adams@oracle.com \
--cc=16491@debbugs.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.