all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Liu <sdl.web@gmail.com>
To: Daniel Colascione <dancol@dancol.org>
Cc: Andy Moreton <andrewjmoreton@gmail.com>, 16402@debbugs.gnu.org
Subject: bug#16402: 24.3.50; Document nadvice.el stuff in Elisp manual before Emacs 24.4
Date: Fri, 10 Jan 2014 12:19:10 +0800	[thread overview]
Message-ID: <m11u0gii4h.fsf@gmail.com> (raw)
In-Reply-To: <52CF6B75.5040206@dancol.org> (Daniel Colascione's message of "Thu, 09 Jan 2014 19:39:33 -0800")

On 2014-01-10 11:39 +0800, Daniel Colascione wrote:
> 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.

I agree. People will have a few dozens of defadvice's in their init
file. I think nadvice might be able to cover 99% of defadvice over time.
The code is at manageable size (a few hindered lines) and looks clean.

But I haven't started using it since I am still mostly using 24.3.

Leo





  parent reply	other threads:[~2014-01-10  4:19 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
2014-01-10  4:18         ` Drew Adams
2014-01-10  4:19         ` Leo Liu [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m11u0gii4h.fsf@gmail.com \
    --to=sdl.web@gmail.com \
    --cc=16402@debbugs.gnu.org \
    --cc=andrewjmoreton@gmail.com \
    --cc=dancol@dancol.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.