What I'd like to be able to do is the following. Say I have the following tree: * level 1 * level 2 * level 3 * level 4 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 Is this possible? I looked in the manual, but couldn't see anything. Thanks, Cian
Cian OConnor <cian.oconnor@gmail.com> 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...
--
Bastien
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 <bastienguerry@googlemail.com> writes:
> Cian OConnor <cian.oconnor@gmail.com> 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...
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
Hi Cian, Cian OConnor <cian.oconnor@gmail.com> writes: > 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. I still would find such a display a bit confusing. > 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. If the purpose of such a temporary display is to make the export render the structure of the narrowed buffer as if it was a top-level subtree, then I agree this is useful. You can already achieve this by selecting the whole narrowed subtree (with transient-mark-mode on) and exporting the region. But maybe a narrowed tree should be considered as a selected region by default... -- Bastien
Bastien <bastienguerry@googlemail.com> writes: > Hi Cian, >> 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. > > If the purpose of such a temporary display is to make the export render > the structure of the narrowed buffer as if it was a top-level subtree, > then I agree this is useful. You can already achieve this by selecting > the whole narrowed subtree (with transient-mark-mode on) and exporting > the region. Not really. Its simply a convenience method that I can probably hack for myself, but didn't want to if it already existed. Its simply when I'm drafting I tend to work in subtrees, and it becomes (for my purposes) quite unwieldy when working with large trees (as I tend to). The indent when I'm working with the narrowed buffer is a waste of space, and it also makes it difficult for me to work out what level I'm working at with a simple eyeball at the structure. However I can quite cheerfully see that this is not something most people would want/need. > But maybe a narrowed tree should be considered as a selected region by > default... Yes it probably should.
A possible workaround: (require 'scroll-lock) (define-key global-map [(control shift up)] 'scroll-lock-previous-line) (define-key global-map [(control shift down)] 'scroll-lock-next-line) (define-key global-map [(control shift right)] 'alpha-scroll-lock-next-char) (define-key global-map [(control shift left)] 'alpha-scroll-lock-previous-char) (defun alpha-scroll-lock-previous-char () (interactive) (scroll-right 1)) (defun alpha-scroll-lock-next-char () (interactive) (scroll-left 1))