From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Is the cascading logic of outlines a feature, or a design bug?
Date: Wed, 28 Dec 2022 00:21:52 -0700 [thread overview]
Message-ID: <CAJcAo8s5NRgE-VNRY-TpeZR+t6vAkG0cFM0JeixCkCRYbh8mGA@mail.gmail.com> (raw)
In-Reply-To: <m1mt78huel.fsf@nobis-it.eu>
stefan's example reminded me that there is another common request,
with :noexportheading kludges, in which you do not export a headline
itself. you could try one of those perhaps.
that assumes you want this for export and not for the .org.
On 12/28/22, Stefan Nobis <stefan-ml@snobis.de> wrote:
> abq@bitrot.link writes:
>
>> Likewise, is the inability to close an org-mode outline section
>> without starting a new section really a feature?
>
> I think so. :)
>
> First, technically, it makes the sections (and their contents) a tree
> instead of a graph (DAG) and trees are easier to understand and
> handle. As sections are a quite essential and important data structure
> of Org, it usually means that it would be hard to change it (meaning
> that it could affect a really big part of the code base).
>
> Another rather technical point is, that most export formats like HTML
> and LaTeX/PDF are also tree like structures (regarding sections).
> Therefore it is quite a challenge to export a DAG like structure to
> these formats.
>
> But also semantically I would say it is a feature. Have you ever seen
> a book, longer web page, or even article (with multiple sections) that
> tries to close one section and continue any previous sibling or its
> parent? I have never seen such kind of textual structuring and my
> guess is, that this would be hard for a reader to understand and
> follow. If the intermediate text is small, just make it a list (maybe
> a description list). If a new (sub-)section seems a good idea, then
> structure everything accordingly and tree-like. For example:
>
> --8<---------------cut here---------------start------------->8---
>
> * Topic
> Some initial words.
> ** Subtopic 1
> More text.
> ** Subtopic 2
> Another paragraph.
> ** Other Aspects
> There may be more to say.
>
> --8<---------------cut here---------------end--------------->8---
>
> IMHO there is always a way to structure sections, such that a tree
> like structure suffices. And IMHO this is easier to read an follow.
>
> If you try to use Org for other kinds of data and this data is
> naturally structured like a DAG (or even a cyclic graph), then I think
> a database or other means are better suited than Org.
>
> --
> Until the next mail...,
> Stefan.
>
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2022-12-28 7:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 6:47 Is the cascading logic of outlines a feature, or a design bug? abq
2022-12-26 7:51 ` tomas
2022-12-26 10:12 ` Ihor Radchenko
2022-12-26 17:23 ` abq
2022-12-26 17:32 ` tomas
2022-12-26 17:36 ` Ihor Radchenko
2022-12-26 18:37 ` tomas
2022-12-27 7:21 ` Marcin Borkowski
2022-12-27 9:00 ` tomas
2022-12-28 6:40 ` Marcin Borkowski
2022-12-28 7:28 ` Heinz Tuechler
2022-12-28 9:29 ` tomas
2022-12-26 12:38 ` Max Nikulin
2022-12-26 17:03 ` abq
2022-12-27 16:02 ` Max Nikulin
2022-12-28 1:52 ` Samuel Wales
2022-12-28 7:14 ` Stefan Nobis
2022-12-28 7:21 ` Samuel Wales [this message]
2022-12-28 8:45 ` Greg Minshall
2022-12-28 9:13 ` Ihor Radchenko
2022-12-28 9:34 ` Greg Minshall
2022-12-28 9:34 ` tomas
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=CAJcAo8s5NRgE-VNRY-TpeZR+t6vAkG0cFM0JeixCkCRYbh8mGA@mail.gmail.com \
--to=samologist@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).