unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Barry Margolin'" <barmar@alum.mit.edu>, <help-gnu-emacs@gnu.org>
Subject: RE: buffer variable values
Date: Sat, 25 Aug 2012 12:40:20 -0700	[thread overview]
Message-ID: <11837C21486E45318C7BBE1DFF672E37@us.oracle.com> (raw)
In-Reply-To: <barmar-033E08.14082925082012@news.eternal-september.org>

> Another issue is backward compatibility.  Perhaps at one time the 
> function was commonly used from programs, but when the preferred 
> alternative was added they put that warning into the 
> documentation.  But the function still has to work properly for
> all the old code that was calling it before this.

Actually, I took a look at the Emacs 20 (distributed) source code before writing
that (non-exhaustive) list.  I didn't mention that point (a valid one), since
even back in Emacs 20 there were only a dozen or so non-interactive uses of it
remaining in the (distributed) source code, and even back then
`insert-buffer-substring' existed.

I might add too that my own impression is that Emacs Dev over the last few
releases has become more "generous" with such admonitions, prohibitions, and
prescriptions.  That's fine, as long as such are taken as guidance and not as
gospel.




      reply	other threads:[~2012-08-25 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-25  7:33 buffer variable values drain
2012-08-25  7:52 ` PJ Weisberg
2012-08-25  8:14   ` drain
2012-08-25 15:01     ` Drew Adams
     [not found]   ` <mailman.7557.1345882485.855.help-gnu-emacs@gnu.org>
2012-08-25 14:38     ` Barry Margolin
     [not found] ` <mailman.7566.1345906894.855.help-gnu-emacs@gnu.org>
2012-08-25 18:08   ` Barry Margolin
2012-08-25 19:40     ` Drew Adams [this message]

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=11837C21486E45318C7BBE1DFF672E37@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=barmar@alum.mit.edu \
    --cc=help-gnu-emacs@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.
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).