From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: section continuation
Date: Thu, 29 Dec 2022 09:57:22 +0100 [thread overview]
Message-ID: <Y61Wctl7a0X6NChC@tuxteam.de> (raw)
In-Reply-To: <86358yu47w.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1979 bytes --]
On Thu, Dec 29, 2022 at 05:01:33PM +1100, Tim Cross wrote:
>
> <tomas@tuxteam.de> writes:
>
> > As far as I am concerned, I don't think the feature is important
> > enough to complexify Org, but (a) I see that there are people who
> > really want it (and offer myself as sparring partner to bounce ideas
> > off) and (b) Org is chock full of features I'd rather not have,
> > but others need badly. Software is like that :-)
> >
>
> I agree. While I can understand it is a feature some users may want, it
> certainly isn't one I'm interested in and I continue to be very
> concerned about the feature growth and increase in complexity I see with
> org. I fear we are losing one of the best features of org - simplicity
> and easy customization for individual needs.
Agreed, so far.
> I find the straight-forward
> nature of a tree structure much simpler to work with than one which will
> be less tree like and more directed graph like.
Strongly disagree.
Both are trees (that's why I prefer to talk about "document model".
It's only so that in Org, only the first child of a section node
can be text, the following must be subsections. In "XML" you just
can intermix subsections and text (actually: any kind of subnodes).
Org is "asymmetric" in this respect: blocks can be mixed freely
with text content (aka paragraphs), sections cannot. But trees
they are all.
> While it is true the
> tree structure found in outline mode does impose some restrictions on
> the document layouts you can use, I think that loss in generality is
> justified by the gain in simplicity and consistency in other processing,
> such as data exports.
I think it is misleading to cast it in terms of "tree" vs "non-tree" and
this may be part of the current confusion's source.
Cheers
[1] "XML" as a shorthand for the unrestricted structure of an XML
document model. Then you can restrict it with DTDs, RelaxNGs
or whatever.
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-12-29 8:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 13:08 section continuation (was: Is the cascading logic of outlines a feature, or a design bug?) abq
2022-12-27 13:57 ` tomas
2022-12-28 2:22 ` Samuel Wales
2022-12-27 14:15 ` section continuation abq
2022-12-27 15:36 ` tomas
2022-12-27 20:22 ` abq
2022-12-28 5:17 ` Ihor Radchenko
2022-12-28 8:58 ` tomas
2022-12-29 6:01 ` Tim Cross
2022-12-29 8:57 ` tomas [this message]
2022-12-29 9:21 ` Heinz Tuechler
2022-12-29 10:09 ` Jean Louis
2022-12-29 10:42 ` Ihor Radchenko
2022-12-29 14:00 ` Jean Louis
2022-12-31 12:16 ` Ihor Radchenko
2022-12-31 12:26 ` tomas
2023-01-01 21:29 ` Tom Gillespie
2022-12-29 10:28 ` tomas
2022-12-31 12:03 ` Greg Minshall
2022-12-29 10:06 ` Jean Louis
2022-12-29 12:47 ` Max Nikulin
2022-12-28 17:37 ` Timothy
2022-12-28 19:34 ` tomas
2022-12-29 10:21 ` Ihor Radchenko
2022-12-29 10:30 ` tomas
2023-01-01 21:19 ` Marcin Borkowski
2022-12-28 20:01 ` Heinz Tuechler
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=Y61Wctl7a0X6NChC@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).