From: Nick Dokos <nicholas.dokos@hp.com>
To: Cian OConnor <cian.oconnor@gmail.com>
Cc: Bastien <bastienguerry@googlemail.com>, emacs-orgmode@gnu.org
Subject: Re: Narrow tSparse Trees layout
Date: Fri, 31 Jul 2009 10:46:06 -0400 [thread overview]
Message-ID: <9011.1249051566@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Cian OConnor <cian.oconnor@gmail.com> of "Fri, 31 Jul 2009 15:22:54 BST." <uprbhx77l.fsf_-_@gmail.com>
Cian OConnor <cian.oconnor@gmail.com> wrote:
>
> 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.
>
I presume you have org-hide-leading-stars set to t. If so, what looks
like indentation, is really hidden leading stars (see section 14.5 of
the manual). I am no expert but I would think that implementing what
you want would be difficult. If it really bothers you, perhaps you can
promote the tree to level 1 while you are working on it and then demote
it before widening again - I think this cure is worse than the disease,
but to each his own.
HTH,
Nick
next prev parent reply other threads:[~2009-07-31 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 21:13 Sparse Trees layout Cian OConnor
2009-07-31 0:10 ` Bastien
2009-07-31 14:22 ` Narrow tSparse " Cian OConnor
2009-07-31 14:46 ` Nick Dokos [this message]
2009-08-02 19:17 ` Bastien
2009-08-04 13:51 ` Cian OConnor
2009-08-04 17:20 ` Samuel Wales
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9011.1249051566@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=bastienguerry@googlemail.com \
--cc=cian.oconnor@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).