From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: 17569@debbugs.gnu.org
Subject: bug#17569: 24.4.50; doc of "wrapper hooks"
Date: Sat, 24 May 2014 17:35:13 -0400 [thread overview]
Message-ID: <jwva9a6zwzl.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <hosinydhfb.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 24 May 2014 16:56:40 -0400")
> wrapper hooks too. (Though in general I don't understand why you delete
> documentation of obsolete features, rather than simply adding a "The
> following refers to an obsolete feature. In new code, use FOO" or
> somesuch at the start.)
I don't think it's worth documenting that which we discourage. But if
you want to document how to replace such code with the new feature,
that's fine.
> filter-buffer-substring-function, completion-in-region-function,
> abbrev-expand-function don't seem to be documented.
`completion-in-region-function' is probably not worth documenting.
But the filter-buffer-substring-functions and abbrev-expand-functions
documentation should be changed indeed to document
filter-buffer-substring-function and abbrev-expand-function instead.
Stefan
next prev parent reply other threads:[~2014-05-24 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<6907e1e1-e802-45cd-adad-917290420cf6@default>
[not found] ` <<9pmwe8t8qq.fsf@fencepost.gnu.org>
[not found] ` <<17297117-eeea-4bca-a9a3-a08cd966d1fb@default>
[not found] ` <<jwvbnun50ay.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <<6bad204d-c3d7-4630-aa7f-1a09288f6ad4@default>
[not found] ` <<83ppj3jjfq.fsf@gnu.org>
2014-05-24 15:57 ` bug#17569: 24.4.50; doc of "wrapper hooks" Drew Adams
2014-05-24 16:21 ` Stefan Monnier
2014-05-24 20:56 ` Glenn Morris
2014-05-24 21:35 ` Stefan Monnier [this message]
2014-05-23 22:30 Drew Adams
2014-05-23 22:45 ` Glenn Morris
2014-05-23 22:53 ` Drew Adams
2014-05-24 3:21 ` Stefan Monnier
2014-05-24 15:03 ` Drew Adams
2014-05-24 15:16 ` Eli Zaretskii
2014-05-24 20:09 ` 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=jwva9a6zwzl.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=17569@debbugs.gnu.org \
--cc=rgm@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.