From: Drew Adams <drew.adams@oracle.com>
To: David Kastrup <dak@gnu.org>, Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: RE: Please post older versions of GNU Emacs manuals on the web
Date: Sun, 3 Jan 2016 08:34:10 -0800 (PST) [thread overview]
Message-ID: <bff73d3a-4166-45c3-9ad7-c21f3404b216@default> (raw)
In-Reply-To: <87lh87j5kb.fsf@fencepost.gnu.org>
> >> In addition, I think the text about defadvice was deleted from the
> >> manual too soon. Just because it is no longer the recommended
> >> interface is no reason to remove it from the Lisp manual.
> >
> > OK, since there seems to be general agreement, how about we pull
> > defadvice back into the manual for 25.1, with a note that has been
> > deprecated.
>
> That seems to make sense. However, Raman stated that nadvice does not
> work for a number of use cases he currently uses defadvice for. That
> hole needs to be filled in some manner eventually, or we will never be
> justified in completing deprecation.
+1
There is also the question of using defadvice to modify a
doc string. AFAICT, that is another hole unfilled by nadvice.
next prev parent reply other threads:[~2016-01-03 16:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 16:46 Please post older versions of GNU Emacs manuals on the web Drew Adams
2016-01-02 17:01 ` Eli Zaretskii
2016-01-02 17:11 ` John Wiegley
2016-01-02 17:19 ` Drew Adams
2016-01-04 3:15 ` Richard Stallman
2016-01-02 23:11 ` Richard Stallman
2016-01-03 3:57 ` John Wiegley
2016-01-03 4:09 ` Drew Adams
2016-01-03 4:18 ` raman
2016-01-03 10:55 ` David Kastrup
2016-01-03 16:34 ` Drew Adams [this message]
2016-01-03 2:07 ` Xue Fuqiao
2016-01-03 3:14 ` raman
2016-01-03 3:32 ` Drew Adams
2016-01-03 7:08 ` Teemu Likonen
[not found] <<1e249214-6831-4c2b-98a4-d16a6d1d7048@default>
[not found] ` <<83a8onc3vc.fsf@gnu.org>
2016-01-02 17:19 ` Drew Adams
2016-01-03 6:33 ` Ivan Shmakov
[not found] ` <<E1aFVL3-0000Fj-8h@fencepost.gnu.org>
2016-01-02 23:16 ` 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=bff73d3a-4166-45c3-9ad7-c21f3404b216@default \
--to=drew.adams@oracle.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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.