emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: abq@bitrot.link
To: emacs-orgmode@gnu.org
Subject: section continuation (was: Is the cascading logic of outlines a feature, or a design bug?)
Date: Tue, 27 Dec 2022 13:08:41 +0000	[thread overview]
Message-ID: <2a8c15a7047e6dd4979b311a5c373255@bitrot.link> (raw)

tomas wrote:
> I already proposed
> having one canonical heading meaning "back to that level", say dash
> or dot

> Now for that to be useful, you'd have to gather enough users who
> like the idea and use the convention. It's a communication medium,
> after all :-)

The question isn't only how people interpret their files, but also how 
their software interprets their files.

Is anyone here aware of anyone who uses a lone dash or dot or comma 
heading for some other purpose? IOW, if future Org versions were to 
treat it as having some special meaning, would it break backward 
compatibility in practice?

So if you fold/select/delete/move/promote/demote/etc a section, it 
processes not only all the subsections, but also all the following 
lone-dash sections at the section's level. If you number sections, 
lone-dash sections don't get numbers.

If you prefer the standard outliner behavior, then just never use 
lone-dash sections.

To bikeshed the character, dash is commonly used in tree viewers to 
indicate a folded heading (with plus sign for unfolded), so maybe a 
different one is better for section continuation. For continuation, 
comma would be more suggestive than period.


             reply	other threads:[~2022-12-27 13:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 13:08 abq [this message]
2022-12-27 13:57 ` section continuation (was: Is the cascading logic of outlines a feature, or a design bug?) 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

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=2a8c15a7047e6dd4979b311a5c373255@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).