From: Josh <josh@foxtail.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Florian Beck <fb@miszellen.de>, 16959@debbugs.gnu.org
Subject: bug#16959: 24.3.50; defadvice docstring out of date
Date: Wed, 12 Mar 2014 09:30:08 -0700 [thread overview]
Message-ID: <CANdFEAHAmOdf515HP+VOGSE_q_NL2nUeNEPDWjfDS6X=8WX3sA@mail.gmail.com> (raw)
In-Reply-To: <jwv7g7z5y3a.fsf-monnier+emacsbugs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
On Wed, Mar 12, 2014 at 6:49 AM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:
> > Some specifics:
>
> Thanks Florian, this list is very helpful. Just one comment:
>
> > - Indeed, it seems the documentation is in the wrong order: from a
> user's
> > perspective, advice-add is what she usually wants and add-function
> > is a special case.
>
> Actually, add-function is likely to become more common with new hooks
> using a `*-function' variable modified via add-function rather than
> a `*-functions' modified via add-hook.
Somewhat relatedly, would you consider renaming advice-add to
add-advice (naturally with an alias for backward compatibility)?
It's easier to discover related functionality through tab
completion, apropos, etc. when its names share a common structure.
For example if I was looking for basename functionality and I knew
about file-name-directory, `C-h f file-name- TAB' would lead me to
`file-name-nondirectory' straightaway.
[-- Attachment #2: Type: text/html, Size: 1419 bytes --]
next prev parent reply other threads:[~2014-03-12 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 15:00 bug#16959: 24.3.50; defadvice docstring out of date Florian Beck
2014-03-10 18:16 ` Glenn Morris
2014-03-11 5:37 ` Florian Beck
2014-03-12 13:49 ` Stefan Monnier
2014-03-12 16:30 ` Josh [this message]
2014-03-12 18:41 ` 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='CANdFEAHAmOdf515HP+VOGSE_q_NL2nUeNEPDWjfDS6X=8WX3sA@mail.gmail.com' \
--to=josh@foxtail.org \
--cc=16959@debbugs.gnu.org \
--cc=fb@miszellen.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.