unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>,
	Jean-Christophe Helary
	<jean.christophe.helary@traduction-libre.org>
Cc: emacs-devel@gnu.org
Subject: RE: *scratch* buffer documentation
Date: Fri, 27 Dec 2019 08:12:34 -0800 (PST)	[thread overview]
Message-ID: <3b80e0e2-8a32-4b88-b412-187fba4a1582@default> (raw)
In-Reply-To: <83v9q2p4oz.fsf@gnu.org>

> How about this addition instead, after the first paragraph:
> 
>   Buffers exist as long as they are used, and are deleted ("killed")
>   when no longer needed, either by you (see Kill Buffer) or by Emacs
>   (e.g., when you exit Emacs, see Exiting).

Minor suggestion (and I agree that it can
help to have some such statement where we
introduce buffers):

"Used" could mislead.  It could give the
impression that a buffer is "no longer
needed" only when it is no longer visible
or is being actively edited by a user.

It's not about whether a user is using the
buffer (or that she thinks she is).

It may not be obvious here that it's about
whether Emacs - anything in Emacs - is
"using" the buffer, i.e., that there is some
reference to it - some need for it.  (But
"reference" might not be clear to some
non-programmers.)

"No longer needed" is probably clear enough,
on its own.  Without saying what that means,
it will likely be interpreted correctly, as
meaning that Emacs (not just a user) needs
the buffer for some reason.

It's OK to be vague about what "need" means,
even if it's not so OK (IMO) to be vague
about what "use" means.  I suggest dropping
mention of being "used".



  parent reply	other threads:[~2019-12-27 16:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24 23:58 *scratch* buffer documentation Jean-Christophe Helary
2019-12-25  1:24 ` Óscar Fuentes
2019-12-25  1:44   ` Jean-Christophe Helary
2019-12-25 14:55 ` Eli Zaretskii
2019-12-26  0:54   ` Jean-Christophe Helary
2019-12-26  2:29     ` arthur miller
2019-12-26  3:00       ` Jean-Christophe Helary
2019-12-26  3:27         ` Óscar Fuentes
2019-12-26  5:19           ` Jean-Christophe Helary
2019-12-26  5:20           ` Jean-Christophe Helary
2019-12-26 16:22     ` Eli Zaretskii
2019-12-26 17:15       ` Jean-Christophe Helary
2019-12-26 17:36         ` Lars Ingebrigtsen
2019-12-26 18:14           ` Jean-Christophe Helary
2019-12-26 20:25         ` Eli Zaretskii
2019-12-27  1:03           ` Jean-Christophe Helary
2019-12-27  8:12             ` Eli Zaretskii
2019-12-27  9:12               ` Jean-Christophe Helary
2019-12-27  9:26                 ` Eli Zaretskii
2019-12-27  9:44                   ` Jean-Christophe Helary
2019-12-27 11:31               ` VanL
2019-12-27 14:06                 ` Eli Zaretskii
2019-12-27 18:24                   ` John Yates
2019-12-27 18:45                     ` Eli Zaretskii
2019-12-27 16:12               ` Drew Adams [this message]
2019-12-27 17:07               ` Lars Ingebrigtsen

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=3b80e0e2-8a32-4b88-b412-187fba4a1582@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@traduction-libre.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).