unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: *scratch* buffer documentation
Date: Thu, 26 Dec 2019 04:27:18 +0100	[thread overview]
Message-ID: <87d0cbepcu.fsf@telefonica.net> (raw)
In-Reply-To: D88DF0A4-06CC-4AC3-8ADC-AFDB452E526D@traduction-libre.org

Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
writes:

>> I Think that you are missing one important thing: users are generally
>> not idiots.
>
> It is not about being idiots or not. But about how self-contained
> should the documentation be.
>
> If you show me the place in the documentation where the default
> behavior is described then I'll need to worry about why I did not find
> it.

  19.4 Killing Buffers

     ‘C-x k’ (‘kill-buffer’) kills one buffer, [...] If you ask to kill
  a file-visiting buffer that is modified, then you must confirm with
  ‘yes’ before the buffer is killed.


A corollary is that other buffers may not trigger the confirmation.

>> Emacs does have its dark corners, but I don't think saving buffers
>
> Indeed, saving buffers is not an issue. It is killing buffers that is.

IMO the implication that Emacs only cares about the persistence of
changes made to file-visiting buffers is clear. If the user, somehow,
expects that Emacs will warn on quitting about changes to *scratch*, he
will swiftly learn what "This buffer is for text that is not saved"
means :-)




  reply	other threads:[~2019-12-26  3:27 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 [this message]
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
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=87d0cbepcu.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --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).