From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Stribblehill Subject: Re: Re: Preventing (or mitigating) accidental deletion in org-mode Date: Sun, 23 Aug 2009 13:30:40 +0100 Message-ID: <1f38ae890908230530u34e4aa4fi31b034174c1d17ae@mail.gmail.com> References: <4A9120DB.6030003@nickbell.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MfCDf-00024s-Sl for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 08:30:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MfCDb-000205-0W for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 08:30:47 -0400 Received: from [199.232.76.173] (port=34420 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MfCDa-0001zT-Pg for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 08:30:42 -0400 Received: from mail-fx0-f226.google.com ([209.85.220.226]:62979) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MfCDa-000354-C3 for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 08:30:42 -0400 Received: by fxm26 with SMTP id 26so1473110fxm.42 for ; Sun, 23 Aug 2009 05:30:40 -0700 (PDT) In-Reply-To: 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: Leo Cc: emacs-orgmode@gnu.org 2009/8/23 Leo : > On 2009-08-23 11:58 +0100, Nick Bell wrote: >> Org-mode is great and I'd like to commit to it. However, I'm held back >> by the apparent fragility of data stored in org-files. For example, >> it's easy to delete entire folded trees of data with just a couple of >> keystrokes or a mouse click. > > This should not be a problem as long as you know how the undo in Emacs > works. You can even use browse-kill-ring=B9 to see what you have deleted = in > Emacs. ...Provided you know that you killed something you didn't intend to. However, it's easy to kill a tree without noticing it had content. Maybe we could augment org-kill-line with some optional facility that checks that it doesn't encompass a collapsed section -- or less intrusively, emits a message saying it's killed a collapsed section. I'm having a hard time seeing how to code it though.