emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Robert Nikander <robert.nikander@icloud.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: text after sub headings?
Date: Thu, 23 Dec 2021 22:10:59 +0000	[thread overview]
Message-ID: <87o857vuoc.fsf@posteo.net> (raw)
In-Reply-To: <43945CE5-F4C3-4DA8-9C0F-EDA40A22A404@icloud.com> (Robert Nikander's message of "Thu, 23 Dec 2021 16:21:42 -0500")

Robert Nikander writes:

> If you view a "*" item as "book section", it's confusing. But if you
> view a "*" item as "collapsible thing", then it makes more sense.

I understand your use case. But I think in that context Org headings
would still be useful (at least they remind us at what level we're). For
example, some headings could be used for those parts with a tag
:not_a_heading:. I sometimes use something like that, and then I remove
those tagged headings on export or convert them to another type of
separator, it depends on the case:

* Top
  Some text under “Top”
  ** A level-2 heading 
    Text under level-2 heading
  ** Another level-2 heading
    Text under the second level-2 heading
* Some descriptive title :not_a_heading:
More text under “Top”

  parent reply	other threads:[~2021-12-23 22:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 21:21 text after sub headings? Robert Nikander
2021-12-23 21:47 ` John Kitchin
2021-12-23 22:10 ` Juan Manuel Macías [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-23 16:11 Robert Nikander
2021-12-23 16:54 ` Max Nikulin
2021-12-23 20:27 ` Juan Manuel Macías
2021-12-24 16:51   ` Max Nikulin
2021-12-24 20:17     ` Juan Manuel Macías
2021-12-25 13:15       ` Max Nikulin
2021-12-26  5:23         ` Ihor Radchenko
2021-12-26  9:17         ` Juan Manuel Macías
2021-12-23 23:12 ` Tim Cross

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:

  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=87o857vuoc.fsf@posteo.net \
    --to=maciaschain@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=robert.nikander@icloud.com \


* 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


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