unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
Cc: emacs-devel@gnu.org
Subject: Re: *scratch* buffer documentation
Date: Fri, 27 Dec 2019 10:12:44 +0200	[thread overview]
Message-ID: <83v9q2p4oz.fsf@gnu.org> (raw)
In-Reply-To: <E8AF6700-FFC5-4A15-8923-3B7115981B27@traduction-libre.org> (message from Jean-Christophe Helary on Fri, 27 Dec 2019 10:03:53 +0900)

> From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
> Date: Fri, 27 Dec 2019 10:03:53 +0900
> 
> ======================================================================
> 19 Using Multiple Buffers
> *************************
> 
> The text you are editing in Emacs resides in a provisory object called a
> “Buffer”.
> ======================================================================
> 
> When I read "provisory" I have alarm bells ringing and I want to know more, so I check the rest of the documentation and indeed, I find the kill command and that confirms that buffers are indeed provisory and need to be saved to a *permanent* file to have their contents archived.
> 
> Would that be an agreeable proposal?

Maybe, except that it cannot be a single word.  We cannot say
"provisory" (a better word is "provisional", btw) without explaining
what it means in this context.  And some might even say that
"provisional" is inaccurate, because that's not exactly the nature of
a buffer: it never changes as long as it exists, so there's no
changing of it later.

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



  reply	other threads:[~2019-12-27  8: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 [this message]
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
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=83v9q2p4oz.fsf@gnu.org \
    --to=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).