From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: *scratch* buffer documentation Date: Thu, 26 Dec 2019 22:25:59 +0200 Message-ID: <837e2irfzc.fsf@gnu.org> References: <69AD1F67-BA40-4342-996E-CAC6CC545E2A@traduction-libre.org> <83lfr0v4ib.fsf@gnu.org> <3B5C95CE-77A8-48DA-BD5D-6BD8D8828C30@traduction-libre.org> <83k16jqcpc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="18365"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 26 21:26:32 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ikZiK-0004fY-3A for ged-emacs-devel@m.gmane.org; Thu, 26 Dec 2019 21:26:32 +0100 Original-Received: from localhost ([::1]:56492 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ikZiI-0004Ao-Vt for ged-emacs-devel@m.gmane.org; Thu, 26 Dec 2019 15:26:31 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42905) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ikZht-0003fC-D7 for emacs-devel@gnu.org; Thu, 26 Dec 2019 15:26:06 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48387) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ikZht-00026C-2Y; Thu, 26 Dec 2019 15:26:05 -0500 Original-Received: from [176.228.60.248] (port=1550 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ikZhr-0002Nm-0e; Thu, 26 Dec 2019 15:26:04 -0500 In-reply-to: (message from Jean-Christophe Helary on Fri, 27 Dec 2019 02:15:16 +0900) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243674 Archived-At: > From: Jean-Christophe Helary > 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.