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: Thu, 26 Dec 2019 22:25:59 +0200	[thread overview]
Message-ID: <837e2irfzc.fsf@gnu.org> (raw)
In-Reply-To: <E24B2F6C-A3E1-4D1C-97F5-5890DC25BB19@traduction-libre.org> (message from Jean-Christophe Helary on Fri, 27 Dec 2019 02:15:16 +0900)

> From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
> Date: Fri, 27 Dec 2019 02:15:16 +0900
> 
> I just tried something:
> 
> create a buffer, type something, kill Emacs.
> 
> Of course, when I restarted Emacs the buffer was gone.
> 
> In any other editor I'd either have a warning that I'm going to lose data or the data would have been automatically saved and would be restored when I restarted the editor.

So maybe you should ask for a new feature, where such a warning will
be displayed.

> 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.  I'm saying that the proper place to document it is
where killing buffers is described.  For example, what happens with
buffers when you exit Emacs is described in "Exiting", where the
manual says:

     “Killing” Emacs means terminating the Emacs program.  To do this,
  type ‘C-x C-c’ (‘save-buffers-kill-terminal’).  A two-character key
  sequence is used to make it harder to type by accident.  If there are
  any modified file-visiting buffers when you type ‘C-x C-c’, Emacs first
  offers to save these buffers.  If you do not save them all, it asks for
  confirmation again, since the unsaved changes will be lost.  Emacs also
  asks for confirmation if any subprocesses are still running, since
  killing Emacs will also kill the subprocesses (*note Shell::).

What you seem to be asking is unreasonable: to have everything related
to buffers in one section.  That will be a very large and confusing
section, lumping many loosely related traits of buffers together.  It
will not be an easy reading at all.

Therefore, we choose to subdivide the complex topic of buffers and
their behavior into several sections, and describe each trait near the
commands and variables related to it.  That makes the manual introduce
the features gradually, and latter reading about each set of related
features much easier.



  parent reply	other threads:[~2019-12-26 20:25 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 [this message]
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
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=837e2irfzc.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).