From: Daniel Colascione <dancol@dancol.org>
To: Alan Mackenzie <acm@muc.de>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 16491@debbugs.gnu.org
Subject: bug#16491: 24.3.50; ?REGRESSION: `defadvice' doc removed from Elisp manual
Date: Wed, 22 Jan 2014 14:20:08 -0800 [thread overview]
Message-ID: <52E04418.9020509@dancol.org> (raw)
In-Reply-To: <20140122221111.GA3185@acm.acm>
On 01/22/2014 02:11 PM, Alan Mackenzie wrote:
> On Sun, Jan 19, 2014 at 09:31:07PM -0500, Stefan Monnier wrote:
>>> At the very least, it [documentation of defadvice] should be
>>> available as an Info manual distributed with Emacs.
>
>> No, we don't document everything, and since documenting is advertising
>> we only document those things which we want people to use.
Moving the documentation to a "deprecated" section --- or even a
separate elisp manual for deprecated functionality --- woudl be a good
compromise.
> How about documenting the things those people want to use? I, for one,
> need defadvice (in CC Mode), and the message coming out is that the
> upcoming Emacs might not be an optimal development platform the way the
> current Emacs is.
>
> Also, how are we encouraging people to convert defadvice to the new
> replacement functions if they can't easily access the former's
> documentation?
What if we did it the other way around and provided a downlevel- and
XEmacs-compatible add-function implementation written in terms of old
defadvice?
next prev parent reply other threads:[~2014-01-22 22:20 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 ` bug#16491: 24.3.50; REGRESSION: `defadvice' doc removed from Elisp manual Drew Adams
2014-01-19 16:58 ` bug#16491: 24.3.50; ?REGRESSION: " 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 [this message]
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=52E04418.9020509@dancol.org \
--to=dancol@dancol.org \
--cc=16491@debbugs.gnu.org \
--cc=acm@muc.de \
--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.