emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: Is the cascading logic of outlines a feature, or a design bug?
Date: Mon, 26 Dec 2022 08:51:38 +0100	[thread overview]
Message-ID: <Y6lSio4njKJzts6N@tuxteam.de> (raw)
In-Reply-To: <fa4ebea85ed72126c753eecc7554a21d@bitrot.link>

[-- Attachment #1: Type: text/plain, Size: 957 bytes --]

On Mon, Dec 26, 2022 at 06:47:37AM +0000, abq@bitrot.link wrote:

> Likewise, is the inability to close an org-mode outline section without
> starting a new section really a feature? [...] 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?

I guess the answer depends on your perspective. Try to reformulate
your question in another way, perhaps then it leads to something.

I must admit I've missed the possibility for Org to continue a
section after a deeper level one from time to time. I've resorted
to "local conventions" (e.g. a headline with "-" as a title).

But all in all, that's what Org's document model is, and you won't
change it because it's (sometimes) more convenient to you. What
you might try is to find enough people to agree in a common way
to work around it, if necessary.

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

next prev parent reply	other threads:[~2022-12-26  7:52 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 [this message]
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=Y6lSio4njKJzts6N@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

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).