From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cassio Koshikumo Subject: Re: Re: Two issues with :VISIBILITY: property Date: Sat, 11 Dec 2010 01:55:51 -0200 Message-ID: References: <87bp4z1pii.fsf@fastmail.fm> <55966220-1F73-41E5-B9FA-A6CE1DC959EE@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=58091 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PRGZE-0000hL-CK for emacs-orgmode@gnu.org; Fri, 10 Dec 2010 22:56:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PRGZD-0003m3-2w for emacs-orgmode@gnu.org; Fri, 10 Dec 2010 22:56:16 -0500 Received: from mail-ww0-f49.google.com ([74.125.82.49]:40082) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PRGZC-0003ll-Uq for emacs-orgmode@gnu.org; Fri, 10 Dec 2010 22:56:15 -0500 Received: by wwb17 with SMTP id 17so4377631wwb.30 for ; Fri, 10 Dec 2010 19:56:13 -0800 (PST) In-Reply-To: <55966220-1F73-41E5-B9FA-A6CE1DC959EE@gmail.com> 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: Carsten Dominik Cc: Matt Lundin , emacs-orgmode@gnu.org Hi, Carsten, I understand what you're saying. I've been looking at the functions responsible for moving trees around and still can't get my head around them. Not that this means much, as I'm just starting to dabble in some elisp and don't have lots of experience with other languages either, but I still see it would require a lot of work. Let's see. If I manage to get a better hold of elisp, maybe I'll try to make a patch. For now, those parenthesis still make my eyes cross... Thanks, 2010/12/9 Carsten Dominik : > Hi Cassio, > > while I agree that it would be nice to keep the detailed > visibility structure of a tree while moving it, the effort > to implement that is rather large. > > Org moves the tree by cutting it out and pasting it back in. > > Outline visibility is done using overlays, not text properties. > Overlays are lost when cutting and pasting text. > > So what one would have to do is save all the overlays, compute > their relative distance to the tree head, and re-install > them after pasting. =A0Possible, but an unproportional > effort in my view. > > Org settles currently for this: > > When a tree is folded entirely, it will be folded after it has > been moved. =A0When it is not folded entirely, then it will > remain unfolded after the pasting. > > I think that this is entirely acceptable, so I don't view > it as a bug. =A0Desirable - maybe yes, but not > important in my view. > > - Carsten > > On Dec 7, 2010, at 1:12 AM, Cassio Koshikumo wrote: > >> Thanks a lot, Matt! The patch did correct the second issue. >> >> About the first one: >> >>> I cannot replicate this. When I move the headlines, they remain folded. >> >> It's strange that you cannot replicate this behavior. I got today's >> snapshot and disabled all my customizations to try a vanilla install, >> and it's still there. >> >> Just to make sure we're talking about the same thing: when you move >> the Level 1 tree (the one that has the PROPERTY drawer) it really >> keeps folded? I ask because I noticed that, if I move one of its >> children, everything remains folded. But if I move the parent tree, >> the entire tree gets expanded. >> >> By the way, it doesn't even take a VISIBILITY setting to cause this. Say= I >> have: >> >> * Chapter 1 >> Text under Chapter 1. >> >> ** Section A >> =A0Text under Section A. >> >> * Chapter 2 >> Text under Chapter 2. >> >> ** Section B >> =A0Text under Section B. >> >> Using S-TAB, I go to OVERVIEW: >> >> * Chapter 1... >> * Chapter 2... >> >> Now I place the cursor on "Chapter 1" and press TAB: >> >> * Chapter 1 >> Text under Chapter 1. >> >> ** Section A... >> >> * Chapter 2... >> >> Right now, "Section A" remains folded, which is what you'd expect >> (because "Chapter 1" is only showing its children). But, if I move >> "Chapter 1" down, putting it after "Chapter 2", "Section A" gets >> expanded: >> >> * Chapter 2... >> >> * Chapter 1 >> Text under Chapter 1. >> >> ** Section A >> =A0Text under Section A. >> >> This behavior is absolutely consistent here... If you really cannot >> replicate it, I wonder what could be causing it in my installation. >> >> Thanks again for your help and time, >> >> -- >> C=E1ssio Koshikumo >> >> _______________________________________________ >> Emacs-orgmode mailing list >> Please use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode > > --=20 C=E1ssio Koshikumo