From: Heinz Tuechler <tuechler@gmx.at>
To: emacs-orgmode@gnu.org
Subject: Re: section continuation
Date: Wed, 28 Dec 2022 21:01:02 +0100 [thread overview]
Message-ID: <c4087eba-d812-7889-15f3-1d49c7bc8bd1@gmx.at> (raw)
In-Reply-To: <874jtfa0jd.fsf@tec.tecosaur.net>
Timothy wrote/hat geschrieben on/am 28.12.2022 18:37:
> Hi all,
>
> 2¢ from me: I have yet to see an example which seems like it actually needs the
> ability to go “up” a level. Sometimes I need to rethink my initial impulses, but
> often it forces me to use a better structure.
>
> Considering the example used in the thread, I would think it lends itself to
> something like this:
>
> ┌────
> │ * General animals
> │ Some text about general animals
> │
> │ ** Categories
> │
> │ *** arthropods
> │ spiders and things
> │
> │ *** vertebrates
> │ so-and-so
> │
> │ *** other animals
> │ etc.
> │
> │ ** Overall comments
> │ More about animals in general
> └────
>
> All the best,
> Timothy
>
Dear Timoty,
taking your example, it seems logically disturbing to me to put "Some
text about general animals" at a different level than "More about
animals in general".
In other words, if "More about animals in general" deserves an "**
Overall comments" section, why should not "Some text about general
animals" be headed by "** Introductory comments"? I don't propose that
solution, but it seems logically more consistent to me. For myself, I
did not find a good solution, but I frequently encounter similar situations.
best regards,
Heinz
prev parent reply other threads:[~2022-12-28 20:02 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
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 [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=c4087eba-d812-7889-15f3-1d49c7bc8bd1@gmx.at \
--to=tuechler@gmx.at \
--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).