From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: *scratch* buffer documentation
Date: Fri, 27 Dec 2019 02:15:16 +0900 [thread overview]
Message-ID: <E24B2F6C-A3E1-4D1C-97F5-5890DC25BB19@traduction-libre.org> (raw)
In-Reply-To: <83k16jqcpc.fsf@gnu.org>
> On Dec 27, 2019, at 1:22, Eli Zaretskii <eliz@gnu.org> wrote:
>
> I hope you now agree that the information about killing unsaved
> buffers is exactly where it should be.
No, because what is important here is not whether a buffer is killed or not, but what are the intrinsic properties of buffers.
What you call "default behavior" and what Óscar calls a corollary of the kill-buffer description comes from the nature of buffers and that nature is not properly explained. That explanation should come as the second sentence of "19 Using Multiple Buffers". Or maybe the second paragraph.
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.
This behavior is specific to Emacs and its buffers and should be properly documented.
Of course, now I don't need that documentation any more since it's been discussed here for the last few hours. So it's likely that I won't forget it. But that's not this kind of information persistence that I'm after.
Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune
next prev parent reply other threads:[~2019-12-26 17:15 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E24B2F6C-A3E1-4D1C-97F5-5890DC25BB19@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.