From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: Is the cascading logic of outlines a feature, or a design bug?
Date: Wed, 28 Dec 2022 10:34:58 +0100 [thread overview]
Message-ID: <Y6wNwu+ZmN05ZwKI@tuxteam.de> (raw)
In-Reply-To: <m1mt78huel.fsf@nobis-it.eu>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
On Wed, Dec 28, 2022 at 08:14:26AM +0100, Stefan Nobis 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 [...]
No. XML is very much a tree yet has "that other" document model. The
difference is whether you allow a node to contain "mixed" (as the
XMLians call it) stuff (nodes and text, basically) or you allow
certain nodes to only have one text element at the very beginning
(Org). Actually, Org is more confusing than that, because inline
markup, blocks and all that /are/ allowed to mix with normal text.
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2022-12-28 9:35 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
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 [this message]
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=Y6wNwu+ZmN05ZwKI@tuxteam.de \
--to=tomas@tuxteam.de \
--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).