From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cian OConnor Subject: Re: Narrow tSparse Trees layout Date: Fri, 31 Jul 2009 15:22:54 +0100 Message-ID: References: <82my6lc1sl.fsf@gmail.com> <877hxplk5r.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MWt2Z-00035g-P2 for emacs-orgmode@gnu.org; Fri, 31 Jul 2009 10:24:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MWt2W-0002yJ-04 for emacs-orgmode@gnu.org; Fri, 31 Jul 2009 10:24:59 -0400 Received: from [199.232.76.173] (port=33416 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MWt2V-0002xj-Dd for emacs-orgmode@gnu.org; Fri, 31 Jul 2009 10:24:55 -0400 Received: from mail-ew0-f211.google.com ([209.85.219.211]:54629) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MWt2V-0002CG-26 for emacs-orgmode@gnu.org; Fri, 31 Jul 2009 10:24:55 -0400 Received: by ewy7 with SMTP id 7so1398918ewy.42 for ; Fri, 31 Jul 2009 07:24:54 -0700 (PDT) In-Reply-To: <877hxplk5r.fsf@bzg.ath.cx> (Bastien's message of "Fri\, 31 Jul 2009 08\:10\:01 +0800") 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: Bastien Cc: emacs-orgmode@gnu.org Oh sorry, I was using the wrong terminology. I don't mean sparse trees at all, I meant narrow trees. It would be nice if there was an option so that narrowed trees are displayed without their normal indentation. So for example if narrow a subtree at level 4, then it is displayed as a normal tree at level 1 rather than as a tree starting at level 4 as currently happens. Its just that when drafting papers I tend to have lots and lots of indentation in early drafts, and while narrowing trees is a godsend, the unnecessary (for my purposes) indentation is slightly annoying. Cian Bastien writes: > Cian OConnor writes: > >> Now if I go to level 3 and create a sparse tree I get this: >> * level 3 >> * level 4 >> >> Which is fine and usable, but it would be nice to have the option to >> have the following instead: >> >> * level 3 >> * level 4 > > Why would you want to have this? > > I find this a bit confusing...