* nested org-headlines
@ 2012-11-27 10:14 42 147
2012-11-28 3:36 ` Eric Abrahamsen
0 siblings, 1 reply; 4+ messages in thread
From: 42 147 @ 2012-11-27 10:14 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
(1) is possible, but not (2) and (3), (3) being what I want (though (2)
would be nice).
(1)
* HEADLINE
Text about main topic.
*************** INLINE TASK
Text about tangent from main topic.
*************** END
Continuation of main topic.
(2)
* HEADLINE
Text about main topic.
*************** INLINE TASK
Text about tangent from main topic.
****************************** NESTED INLINE TASK
Text about tangent from tangent from main topic.
****************************** END
Text about tangent from main topic continued.
*************** END
Continuation of main topic.
(3)
* HEADLINE
Text about main topic.
*************** INLINE TASK
Text about tangent from main topic
** SECOND-ORDER HEADLINE ABOUT TANGENT
Text about sub-topic mentioned in tangent
** ANOTHER SECOND-ORDER HEADLINE ABOUT TANGENT
Text about a different sub-topic mentioned in tangent.
[no return to the first-order tangent]
*************** END
Continuation of main topic.
[-- Attachment #2: Type: text/html, Size: 1357 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: nested org-headlines
2012-11-27 10:14 nested org-headlines 42 147
@ 2012-11-28 3:36 ` Eric Abrahamsen
2012-11-28 13:19 ` Nicolas Goaziou
0 siblings, 1 reply; 4+ messages in thread
From: Eric Abrahamsen @ 2012-11-28 3:36 UTC (permalink / raw)
To: emacs-orgmode
42 147 <aeuster@gmail.com> writes:
> (1) is possible, but not (2) and (3), (3) being what I want (though
> (2)
> would be nice).
I was going to say you could use drawers instead of inline tasks (see
section 2.8 of the manual), but they don't nest properly: if you put one
inside the other and fold the outer one, it only folds to the next
:END:. So if you've got this:
#+DRAWERS: SOMEDRAWER ANOTHER
* Header
:SOMEDRAWER:
Some stuff.
:ANOTHER:
More stuff here.
:END:
Some more stuff.
:END:
TAB on the top drawername gives you this:
:SOMEDRAWER:...
Some more stuff.
:END:
Rather than this:
:SOMEDRAWER:...
:END:
Regular org uses `org-flag-drawer' for this, which just searches for the
next :END: string. I thought org elements might handle it differently,
but `org-element-drawer-parser' just does the same thing: searches for
the next :END: string.
If drawers are "greater elements" in org elements, perhaps they ought to
be able to contain other drawers? Or is non-nesting drawers a design
decision?
E
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: nested org-headlines
2012-11-28 3:36 ` Eric Abrahamsen
@ 2012-11-28 13:19 ` Nicolas Goaziou
2012-11-28 13:54 ` Eric Abrahamsen
0 siblings, 1 reply; 4+ messages in thread
From: Nicolas Goaziou @ 2012-11-28 13:19 UTC (permalink / raw)
To: Eric Abrahamsen; +Cc: emacs-orgmode
Hello,
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> If drawers are "greater elements" in org elements, perhaps they ought to
> be able to contain other drawers? Or is non-nesting drawers a design
> decision?
It is a design decision.
Note that "greater element" only means that the element can contain
other elements (i.e. a paragraph.). Also, according to org-element.el
comments:
With the exception of `headline' and `item' types, greater elements
cannot contain other greater elements of their own type.
A drawer is a way to hide some contents (and optionally remove them from
export) without adding any specific meaning to them. What would a drawer
within another drawer mean: hide stuff even more?
Also, adding recursive drawers has a cost (for parsing speed, with
visibility cycling features...) with no real benefit, which explains why
it wasn't implemented.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: nested org-headlines
2012-11-28 13:19 ` Nicolas Goaziou
@ 2012-11-28 13:54 ` Eric Abrahamsen
0 siblings, 0 replies; 4+ messages in thread
From: Eric Abrahamsen @ 2012-11-28 13:54 UTC (permalink / raw)
To: emacs-orgmode
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> If drawers are "greater elements" in org elements, perhaps they ought to
>> be able to contain other drawers? Or is non-nesting drawers a design
>> decision?
>
> It is a design decision.
>
> Note that "greater element" only means that the element can contain
> other elements (i.e. a paragraph.). Also, according to org-element.el
> comments:
>
> With the exception of `headline' and `item' types, greater elements
> cannot contain other greater elements of their own type.
That's a good thing to know.
> A drawer is a way to hide some contents (and optionally remove them from
> export) without adding any specific meaning to them. What would a drawer
> within another drawer mean: hide stuff even more?
Makes plenty of sense to me. But it's not the first time someone's asked
about ways of descending from one text level into a sub-hierarchy, and
then "popping" back out to the previous textual level. When the will is
there, tools will be abused...
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-11-28 13:50 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-11-27 10:14 nested org-headlines 42 147
2012-11-28 3:36 ` Eric Abrahamsen
2012-11-28 13:19 ` Nicolas Goaziou
2012-11-28 13:54 ` Eric Abrahamsen
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).