emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: section continuation
Date: Tue, 27 Dec 2022 16:36:59 +0100	[thread overview]
Message-ID: <Y6sRG/iDsCrvjLqQ@tuxteam.de> (raw)
In-Reply-To: <9ceaa25e9e84c9c2db5cb385c51eb1db@bitrot.link>

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

On Tue, Dec 27, 2022 at 02:15:26PM +0000, abq@bitrot.link wrote:
> 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

Hm. To me, it would be less intuitive (the material under this
pseudo heading is intended to be level 1, not 2). So you might
like to add this to the costs. Or not, if that doesn't make
sense to you :)

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

Don't count my use case. It is well localised, and shouldn't interfere
with a choice of character. You had one more compelling downside of
dash (for dot: perhaps it looks too much like the ellipsis of a folded
subsection). I actually liked the comma, which has already a job as
an escape-character for line constructs in Org.

But we are already bikeshedding: I'd leave that for when you have
enough users. Two people bikeshedding isn't enough fun :)

Cheers
-- 
t

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

  reply	other threads:[~2022-12-27 15:38 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 [this message]
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=Y6sRG/iDsCrvjLqQ@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
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).