unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: 16402@debbugs.gnu.org, Andy Moreton <andrewjmoreton@gmail.com>
Subject: bug#16402: 24.3.50; Document nadvice.el stuff in Elisp manual before Emacs 24.4
Date: Thu, 09 Jan 2014 19:39:33 -0800	[thread overview]
Message-ID: <52CF6B75.5040206@dancol.org> (raw)
In-Reply-To: <m1d2k0ikhl.fsf@gmail.com>

On 01/09/2014 07:28 PM, Leo Liu wrote:
> On 2014-01-10 10:29 +0800, Andy Moreton wrote:
>> As the author of nadvice.el, I would have thought that it was incumbent
>> upon you to provide adequate documentation. A rationale to explain why
>> the existing advice package needs changing would also be helpful.
>
> In Stefan's defence this is him saying help me out. I am sure as the
> maintainer of emacs he has plenty in his plate that some lower-priority
> tasks may have to fall in others hands ;)

It'd be easier to document nadvice if there were a clear reason for it 
to exist. Regular advice works fine and has for a long time. It's very 
well documented has many useful features. It integrates with help. It 
supports various interactive commands. I have no plans to use nadvice 
myself any time soon and oppose deprecating regular advice.





  reply	other threads:[~2014-01-10  3:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09  6:06 bug#16402: 24.3.50; Document nadvice.el stuff in Elisp manual before Emacs 24.4 Drew Adams
2014-01-09  6:21 ` 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 [this message]
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=52CF6B75.5040206@dancol.org \
    --to=dancol@dancol.org \
    --cc=16402@debbugs.gnu.org \
    --cc=andrewjmoreton@gmail.com \
    /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).