all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 17569@debbugs.gnu.org
Subject: bug#17569: 24.4.50; doc of "wrapper hooks"
Date: Sat, 24 May 2014 18:16:41 +0300	[thread overview]
Message-ID: <83ppj3jjfq.fsf@gnu.org> (raw)
In-Reply-To: <6bad204d-c3d7-4630-aa7f-1a09288f6ad4@default>

> Date: Sat, 24 May 2014 08:03:26 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 17569@debbugs.gnu.org
> 
> And what about a function, such as `filter-buffer-substring',
> whose implementation and doc string makes use of such a var?
> What is being recommended now for someone who wants the
> functionality of `filter-buffer-substring' - just roll your own?

Using obsolete variables or functions doesn't automatically make their
users obsolete.  It just means they need to be fixed by changing their
implementation to use the alternative non-obsolete replacements.
Therefore, there's no need to stop using those APIs that use obsolete
vars.






  reply	other threads:[~2014-05-24 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 22:30 bug#17569: 24.4.50; doc of "wrapper hooks" 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 [this message]
2014-05-24 20:09       ` Drew Adams
     [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           ` Drew Adams
2014-05-24 16:21             ` Stefan Monnier
2014-05-24 20:56               ` Glenn Morris
2014-05-24 21:35                 ` 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=83ppj3jjfq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17569@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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.