unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Yates <john@yates-sheets.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: VanL <van@scratch.space>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: *scratch* buffer documentation
Date: Fri, 27 Dec 2019 13:24:56 -0500	[thread overview]
Message-ID: <CAJnXXogsFbD3_UZHfcZGQWSS8581G0=Dx0WzFPgqVUqgoLzS4A@mail.gmail.com> (raw)
In-Reply-To: <83eewpq2w6.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

Jumping in after having read only the last few post in the thread.

How about "nonpersistent"?

/john

On Fri, Dec 27, 2019 at 9:06 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: VanL <van@scratch.space>
> > Date: Fri, 27 Dec 2019 22:31:22 +1100
> >
> > >> 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.
> >
> > The intro to RPi4B uses the words 'volatile' and 'non-volatile' memory.
>
> Buffers aren't "volatile", either, they don't evaporate unless killed.
>
>

-- 
John Yates
505 Tremont St, #803
Boston, MA 02116

[-- Attachment #2: Type: text/html, Size: 1784 bytes --]

  reply	other threads:[~2019-12-27 18:24 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 [this message]
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='CAJnXXogsFbD3_UZHfcZGQWSS8581G0=Dx0WzFPgqVUqgoLzS4A@mail.gmail.com' \
    --to=john@yates-sheets.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=van@scratch.space \
    /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).