From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: Re: Unhiding edited areas Date: Thu, 30 Jul 2009 11:10:13 -0700 Message-ID: <20524da70907301110m208bc575jc1f18de4460cc56e@mail.gmail.com> References: <4A71BF50.2050401@os.inf.tu-dresden.de> 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 1MWa56-0002QB-Fl for emacs-orgmode@gnu.org; Thu, 30 Jul 2009 14:10:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MWa51-0002JJ-LL for emacs-orgmode@gnu.org; Thu, 30 Jul 2009 14:10:19 -0400 Received: from [199.232.76.173] (port=60192 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MWa51-0002J2-Fq for emacs-orgmode@gnu.org; Thu, 30 Jul 2009 14:10:15 -0400 Received: from an-out-0708.google.com ([209.85.132.249]:58131) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MWa51-0001qL-4Y for emacs-orgmode@gnu.org; Thu, 30 Jul 2009 14:10:15 -0400 Received: by an-out-0708.google.com with SMTP id b6so1486984ana.21 for ; Thu, 30 Jul 2009 11:10:14 -0700 (PDT) In-Reply-To: <4A71BF50.2050401@os.inf.tu-dresden.de> 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: Martin Pohlack Cc: emacs-orgmode@gnu.org Hi Martin, This is a huge issue.[1] Here is what I do to try to work around it. I use git, to limit the damage from confusion. I expand the entire buffer if I think I am about to be confused. ;;i like the idea of clustering undo but find it disconcerting (setf org-self-insert-cluster-for-undo nil) ;;somebody, I think Carsten, suggested this, and it might work for you, but for some reason I commented it out. I don't remember what the reason was. Maybe speed. '(defadvice undo (after org-undo-reveal activate) "Make point and context visible after an undo command in Org-mode." (and (org-mode-p) (org-reveal))) ;;(ad-unadvise 'undo) [1] It is even more important when combined with what is IMO Emacs's greatest need for improvement, which is that you can undo, and undo an undo, and this is considered to be sufficient since you can get anywhere in the timeline in principle -- but many users, myself included, prefer a true redo command, both because undoing an undo does not let you do commands (such as copying) in the middle of an undo sequence without going the other direction, and because it feels more intuitive to tell emacs where in the timeline we want to go, and go forward or backward if we overshoot, thus making it possible to view the timeline the same way as we go backward and forward in any linear sequence. (redo.el provides the functionality, but it corrupts the buffer.) Of course, many are comfortable with the traditional undo-the-undo mechanism, so that should stay possible, but there are many who are not, and a redo mechanism would satisfy them. It is possible to get more fancy with a tree. -- Myalgic encephalomyelitis makes you die decades early (Jason et al. 2006) and suffer severely. Conflicts of interest are destroying research. What people "know" is wrong. Silence = death. http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm