From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: section continuation
Date: Thu, 29 Dec 2022 19:47:32 +0700 [thread overview]
Message-ID: <tok295$695$1@ciao.gmane.io> (raw)
In-Reply-To: <248c92c57142c9119ce0b6f51b41da46@bitrot.link>
On 28/12/2022 03:22, abq@bitrot.link wrote:
> Second, did I cover all the necessary changes to make
> section-continuation generally useful? I.e.
> Skip folding of lone-dash sections when folding all the sections at
> their level.
> Unfold them when unfolding the containing section.
> Skip them when jumping to next/previous section.
> Skip numbering them.
> Display them at one level shallower than currently standard in
> org-indent-mode.
- Various operations with subtrees: kill, yank, refile
- Getting refile/goto targets
and perhaps more functions spread over Org .el files. That is why it is
hardly viable as a 3rd party extension.
It still would be a tree, but with interleaved block-level text elements
and subheadings, while currently subheadings must follow heading text.
What is more close to graph is org-transclusion.
Certainly more liberal structure may confuse readers. It has advantages
for early drafts and notes more close to mind maps. During collection of
notes it can not be anticipated which peace of information will be
expanded with a lot of details. Before publishing document should be
reworked to make it more linear.
HTML documents may be more interactive and have more decorations than
printed papers, so I am unsure concerning the export common denominator
argument. There is a variant of continue parent section for poors:
create a 1 level deeper subsection "<title> (continued)".
I am still in doubts if increased complexity and performance impact
outweigh benefits.
next prev parent reply other threads:[~2022-12-29 13:07 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 [this message]
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='tok295$695$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--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).