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



> On Dec 27, 2019, at 5:25, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> 
>> This behavior is specific to Emacs and its buffers and should be properly documented.
> 
> It _is_ documented.  The disagreement between us is _where_ should it
> be documented.

Eli,

I am starting to see where the disagreement is.

> What you seem to be asking is unreasonable: to have everything related
> to buffers in one section.

What about a 1-word addition? The File Handling section has the word "permanent" in it:

======================================================================
18 File Handling
****************

The operating system stores data permanently in named “files”, so most
of the text you edit with Emacs comes from a file and is ultimately
stored in a file.
======================================================================


What about adding a word that indicates the temporary nature of buffers as a qualifier to "object" in Using Multiple Buffers?

That way we have a clear opposition early in the description of the two objects and that would help discovery/understanding the other traits of buffers.

There are a number of words that fit the description. The antonym of "permanent" seems to be "temporary" and synonyms of "temporaty" are "transient," "ephemeral," "transitory," "provisory" and a few others. I like "provisory" because it implies a condition to change the status of the buffer.

So what about something like that:

======================================================================
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?


Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune





  reply	other threads:[~2019-12-27  1:03 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 [this message]
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
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=E8AF6700-FFC5-4A15-8923-3B7115981B27@traduction-libre.org \
    --to=jean.christophe.helary@traduction-libre.org \
    --cc=emacs-devel@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 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).