From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eddward DeVilla" Subject: Is per-node collapsed state realistic in org-more Date: Wed, 25 Oct 2006 11:53:12 -0500 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gcm0G-0006oh-4B for emacs-orgmode@gnu.org; Wed, 25 Oct 2006 12:53:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gcm0B-0006oM-Jw for emacs-orgmode@gnu.org; Wed, 25 Oct 2006 12:53:19 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gcm0B-0006oJ-Gv for emacs-orgmode@gnu.org; Wed, 25 Oct 2006 12:53:15 -0400 Received: from [66.249.92.175] (helo=ug-out-1314.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gcm0B-0000WU-Gj for emacs-orgmode@gnu.org; Wed, 25 Oct 2006 12:53:15 -0400 Received: by ug-out-1314.google.com with SMTP id 36so156047uga for ; Wed, 25 Oct 2006 09:53:13 -0700 (PDT) Content-Disposition: inline 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 Hi, I have a potentially crazy feature request. There's a feature I liked in a previous outliner I use that I kinda miss in org. In that outliner, each node had it's own state as to whether or not is was collapsed, such that you could collapse a node and it's children would disappear, but when you expand the node, the children would be expanded or collapsed as they had been before the parent was collapsed. Like so: * some headline * the current headline * collapsed child ... * expanded child I'm out going! If you where to collapse 'the current headline' above you would see as you would expect: * some headline * the current headline ... If you were to expend it again you see the first example again: * some headline * the current headline * collapsed child ... * expanded child I'm out going! and not: * some headline * the current headline * collapsed child This is better left unseen! * expanded child I'm out going! Would it be hard to fit this into org? What would be even better is if there might be a way to save that state, but I think that would go against the plain text format of org files. Edd