From: Tim Cross <email@example.com>
Subject: Re: text after sub headings?
Date: Fri, 24 Dec 2021 10:12:29 +1100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Robert Nikander <email@example.com> writes:
> I see why this is not possible, given the text format of an org file. But I am curious if people think it would be useful. This is a bit off-topic maybe, but I’m imagining what I would do if I created something like org-mode using another underlying format.
> * Top
> Some text under “Top”
> ** A level-2 heading
> Text under level-2 heading
> ** Another level-2 heading
> Text under the second level-2 heading
> More text under “Top”
> So if the level-2 headings were collapsed we would still see this.
> ** Could have more sub-headings here
> More top level text, etc.
While I can see how the structure you suggest could be useful in some
use cases, the big drawback is that to implement this, you would have to
add some new 'marker' to indicate where the contents of a
section/sub-section end. Personally, I would find the need to add
section end markers more inconvenient than having this feature, which is
something I would probably only use very rarely. I also suspect it would
have a processing penalty as org would now need to search for and track
matching end markers for each section rather than just searching for
another heading marker of the same level when performing folding.
In my use cases, it is extremely rare to have a situation where I have
sub headings and want to add something at the end which is part of the
parent heading, but which must follow the sub headings. Where I have
found such a structure useful, the contents of the sub headings tend to
be small and more suitable either for a list or one of the other
#+begin_* block types.
One of the original benefits of org mode was simplicity and a basis
built on simple text files. Maintaining that simplicity requires loss of
some flexibility. The more we complicate the model, the less simple it
remains and the more bugs we get.
next prev parent reply other threads:[~2021-12-23 23:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 16:11 text after sub headings? Robert Nikander
2021-12-23 16:54 ` Max Nikulin
2021-12-23 20:27 ` Juan Manuel Macías
2021-12-24 16:51 ` Max Nikulin
2021-12-24 20:17 ` Juan Manuel Macías
2021-12-25 13:15 ` Max Nikulin
2021-12-26 5:23 ` Ihor Radchenko
2021-12-26 9:17 ` Juan Manuel Macías
2021-12-23 23:12 ` Tim Cross [this message]
2021-12-23 21:21 Robert Nikander
2021-12-23 21:47 ` John Kitchin
2021-12-23 22:10 ` Juan Manuel Macías
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).