From: abq@bitrot.link
To: emacs-orgmode@gnu.org
Subject: Is the cascading logic of outlines a feature, or a design bug?
Date: Mon, 26 Dec 2022 06:47:37 +0000 [thread overview]
Message-ID: <fa4ebea85ed72126c753eecc7554a21d@bitrot.link> (raw)
https://orgmode.org/worg/org-faq.html#closing-outline-sections answers
the question:
"Can I close an outline section without starting a new section?"
The answer given is:
"no. Org-mode adheres to the cascading logic of outlines, in which a
section is closed only by another section that occupies an equal or
greater level."
Is that limitation a feature, or a design bug? E.g. if someone proposes
enhancing the Unix directory system to support multiple files with the
same filename in one directory, the proposal would be rejected, with the
explanation that the limitation of only one file per filename is a
feature, not a bug, since it enables the name to uniquely identify the
file. (If you want to claim it's a bug, please at least edit your
subject line, or preferably start a new thread.)
Likewise, is the inability to close an org-mode outline section without
starting a new section really a feature? If so, what benefit does the
restriction provide, that would be lost by relaxing the restriction? Or
is the restriction really just a bug with seniority, and the difficulty
of fixing it (or the compatibility headaches caused by fixing it) would
outweigh the benefits?
Andy
next reply other threads:[~2022-12-26 7:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 6:47 abq [this message]
2022-12-26 7:51 ` Is the cascading logic of outlines a feature, or a design bug? 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
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=fa4ebea85ed72126c753eecc7554a21d@bitrot.link \
--to=abq@bitrot.link \
--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).