From: Drew Adams <drew.adams@oracle.com>
To: 16402@debbugs.gnu.org
Subject: bug#16402: 24.3.50; Document nadvice.el stuff in Elisp manual before Emacs 24.4
Date: Wed, 8 Jan 2014 22:06:54 -0800 (PST) [thread overview]
Message-ID: <e77c6a9b-b9ee-4071-a77c-39cea61a103f@default> (raw)
It seems that whenever users ask a function-advising question anywhere,
Stefan lets them know that `defadvice' is nearly deprecated and not
really being bug-fixed or developed further. He advises ;-) them to use
the `nadvice.el' features (e.g., `add-function') instead.
Wunderbar. But meanwhile, there is nothing in the manual about any of
the new stuff. Still, users are being discouraged from using `defadvice'.
This is not right. The new advice functionality should be fully
documented, and that should be done before advising people here and
there to use the new and abandon the old.
This bug report is to ask for full doc of `nadvice.el' features in the
Elisp manual in the Emacs 24.4 release.
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2014-01-01 on ODIEONE
Bzr revision: 115827 eggert@cs.ucla.edu-20140101192741-bi5hb4xb4kdi2zpw
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-09 6:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 6:06 Drew Adams [this message]
2014-01-09 6:21 ` bug#16402: 24.3.50; Document nadvice.el stuff in Elisp manual before Emacs 24.4 Glenn Morris
2014-01-09 16:01 ` Stefan Monnier
2014-01-10 2:29 ` Andy Moreton
2014-01-10 3:28 ` Leo Liu
2014-01-10 3:39 ` Daniel Colascione
2014-01-10 4:18 ` Drew Adams
2014-01-10 4:19 ` Leo Liu
2014-01-10 14:42 ` Stefan Monnier
2014-01-10 15:15 ` Drew Adams
2014-01-10 21:21 ` Daniel Colascione
2014-01-10 21:50 ` 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=e77c6a9b-b9ee-4071-a77c-39cea61a103f@default \
--to=drew.adams@oracle.com \
--cc=16402@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 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).