From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: a small remember suggestion Date: Sat, 21 Mar 2009 12:28:46 -0700 Message-ID: <20524da70903211228o8ef4b21pc9a287ecd923383c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ll6sX-0004ye-9E for emacs-orgmode@gnu.org; Sat, 21 Mar 2009 15:29:09 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ll6sS-0004yS-UG for emacs-orgmode@gnu.org; Sat, 21 Mar 2009 15:29:08 -0400 Received: from [199.232.76.173] (port=46524 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ll6sS-0004yP-Q1 for emacs-orgmode@gnu.org; Sat, 21 Mar 2009 15:29:04 -0400 Received: from wa-out-1112.google.com ([209.85.146.180]:11317) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ll6sQ-0001yN-H5 for emacs-orgmode@gnu.org; Sat, 21 Mar 2009 15:29:03 -0400 Received: by wa-out-1112.google.com with SMTP id j40so883766wah.26 for ; Sat, 21 Mar 2009 12:29:01 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org org-remember -- use a file On more than one occasion, I have composed something using org-remember, and mistakenly hit a key for killing the buffer. With all buffers except org-remember, this kills a buffer if it has no unsaved text, and asks what buffer to kill if it does, at which point I quit. With org-remember, the buffer has unsaved text, but it is not associated with a file, so it loses text. Text is probably lost upon a crash also. My suggestion is this. Perhaps org-remember can have a file (this fixes the killing problem), and that file can be autosaved (this fixes the crash problem).[fn:4] There is one more case in which text is lost. You might run org-remember from org-remember and not undo. My existing proposal is to allow calling o-r from o-r. I think that solves it. In such a case, however, it will be necessary to allow more than one such file. [fn:4] In principle, if the target location is known, the file can be an indirect buffer into that buffer. This has other advantages, including having all in-buffer settings work, being able to isearch, having a crashed org-remember stay where it is supposed to be (albeit unfinished) and so on. But it wouldn't be necessary to get that fancy. Just any file would work. -- Myalgic encephalomyelitis denialism is causing death (decades early; Jason et al. 2006) and severe suffering (worse than nearly all other diseases studied; e.g. Schweitzer et al. 1995) and grossly corrupting science. http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm