From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Porter Subject: Re: Emacs bug 37890; killing capture buffer Date: Fri, 13 Dec 2019 23:05:51 -0600 Message-ID: <874ky3sdhs.fsf@alphapapa.net> References: <87r217lwwz.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57806) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ifzd2-0000Ii-Hp for emacs-orgmode@gnu.org; Sat, 14 Dec 2019 00:06:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ifzd1-0002KM-Ky for emacs-orgmode@gnu.org; Sat, 14 Dec 2019 00:06:08 -0500 Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:48814 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ifzd1-0002Hb-Bw for emacs-orgmode@gnu.org; Sat, 14 Dec 2019 00:06:07 -0500 Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1ifzcx-000EaE-5y for emacs-orgmode@gnu.org; Sat, 14 Dec 2019 06:06:03 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Michael Heerdegen writes: > Or (really better IMHO) consider a different implementation where the > original buffer is not modified until the user explicitly confirms the > stuff to capture with C-c C-c. That would be helpful in some ways, but harmful in others. For example, consider a capture that is started while in a meeting, on a phone call, away from one's desk, etc., with some notes in it, clock start time, etc. (You can find examples of this workflow in, e.g. Bernt Hansen's Org config.) If Emacs were interrupted (crash, power failure, reboot, etc), the un-finalized capture would still be present in the auto-save file and could be recovered when restarting Emacs and finding the file again. But if the original buffer were not modified until the capture is finalized, where would the unfinalized data be, and how would it be recovered into the desired capture location? The way Org uses indirect, narrowed buffers for capturing is an elegant use of Emacs features that helps protect user data from accidental loss.