From: abq@bitrot.link
To: emacs-orgmode@gnu.org
Subject: Re: section continuation
Date: Tue, 27 Dec 2022 14:15:26 +0000 [thread overview]
Message-ID: <9ceaa25e9e84c9c2db5cb385c51eb1db@bitrot.link> (raw)
In-Reply-To: <2a8c15a7047e6dd4979b311a5c373255@bitrot.link>
Another idea:
Your example was:
* General animals
Some text about general animals
** arthropods
spiders and things
* -
More about animals in general
** vertebrates
so-and-so
But to express your intended meaning, how about this instead:
* General animals
Some text about general animals
** arthropods
spiders and things
** -
More about animals in general
** vertebrates
so-and-so
Note the extra asterisk before the dash.
The benefits:
Even current org-mode software handles
fold/select/delete/move/promote/demote/etc, including continuations
(lone-dash sections), as intended.
No interference with section numbering at the level of the continued
section.
The costs:
For current software, this interferes with section numbering at the
subsection level, since continuations count as subsections.
Commands to jump to next/previous section will include continuations.
Folding subsections will fold continuations.
IMO, the benefits outweigh the costs, because the benefits prevent
problems with editing when using current software, and the costs only
cause problems with viewing and navigation.
Future versions of Org could:
Skip numbering of lone-dash sections.
Skip folding them when folding subsections.
Skip them when jumping to next/previous section.
Display them at one level shallower than currently standard in
org-indent-mode, and maybe omit display of the lone-dash line itself.
BTW, this would be another reason to use a character other than dash,
because you already use dash for an incompatible meaning.
next prev parent reply other threads:[~2022-12-27 14:16 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 ` abq [this message]
2022-12-27 15:36 ` section continuation 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
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=9ceaa25e9e84c9c2db5cb385c51eb1db@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).