From: Robert Nikander <firstname.lastname@example.org> To: email@example.com Subject: Re: text after sub headings? Date: Thu, 23 Dec 2021 16:21:42 -0500 [thread overview] Message-ID: <43945CE5-F4C3-4DA8-9C0F-EDA40A22A404@icloud.com> (raw) Max Nikulin wrote: > Have you seen the following and links therein? > https://orgmode.org/worg/org-faq.html#closing-outline-sections No, I hadn't found that. Thanks. Those links answer my question. Juan Manuel Macías wrote: > It is an interesting question; however, I would say that this is not a > useful or realistic structure. Regardless of the Org trees/subtrees and > their folding ability (indicating that each thing is at a certain > level), I think that a content will be more useful and intelligible if > […] I see your point. Maybe it depends on how you use org-mode and how you imagine the meaning of the "*" items. I see some disagreement about this in the old threads that Max linked to. No need to rehash it deeply here again; I was just curious. The way I'm using org-mode so far, I'm not exporting to other formats, and I can see a use for collapsible sections in the middle of a larger chunk of text. I can already kind of do it with a "-" list item, like this. (Or other things like code blocks, etc) * Heading Top Text Top Text - Sub This can be hidden if I hit 'tab' key on "Sub". More Top Text More Top Text 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.
next reply other threads:[~2021-12-23 21:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-23 21:21 Robert Nikander [this message] 2021-12-23 21:47 ` John Kitchin 2021-12-23 22:10 ` Juan Manuel Macías -- 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: 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=43945CE5-F4C3-4DA8-9C0F-EDA40A22A404@icloud.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: text after sub headings?' \ /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
Code repositories for project(s) associated with this 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).