From: "Juan Manuel Macías" <firstname.lastname@example.org> To: Robert Nikander <email@example.com> Cc: orgmode <firstname.lastname@example.org> Subject: Re: text after sub headings? Date: Thu, 23 Dec 2021 20:27:28 +0000 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <9881E3B7-A1F0-4C0F-AED6-893368A6FEA0@icloud.com> (Robert Nikander's message of "Thu, 23 Dec 2021 11:11:37 -0500") Hi Robert, Robert Nikander writes: > I see why this is not possible, given the text format of an org file. > But I am curious if people think it would be useful. This is a bit > off-topic maybe, but I’m imagining what I would do if I created > something like org-mode using another underlying format. > > Example: > > * 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 > More text under “Top” > So if the level-2 headings were collapsed we would still see this. > ** Could have more sub-headings here > More top level text, etc. 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 it is easy and obvious to extract a table of contents (with headings and levels) from that content. Let's imagine not we are in Org but writing a novel on a typewriter. It could be a two-voice novel, with a main narrator and a "secondary" narrator. The first structure could be: Part I (Narrator A) Some text under Part I (Narrator A) Chaper 1 Text under Chapter 1 (Narrator B) Chapter 2 Text under Chapter 2 (Narrator B) ?? More text under Part I (Narrator A) More chapters (Narrator B) ?? More Part I text, etc. (Narrator A) (...) Although we feel that our structure is very clear, our publisher will probably force us to include some kind of division into the texts marked with "??". I mean, it's not that easy to escape from the (graphical) levels, parts and chapters, even if it is by editorial imposition or for not confuse our readers. We can, for example, call Part II "Interlude", or add the first text marked with "??" after a graphic separation (some dashes, for example: ------). Although the literary structure is complex, its graphical representation always has limits: Part I (Narrator A) Some text under Part I (Narrator A) Chaper 1 Text under Chapter 1 (Narrator B <= Narrator A) Chapter 2 Text under Chapter 2 (Narrator B <= Narrator A) Division 1 (forced by the publishing house = Part II?) More text under Part II (Narrator A) More chapters (Narrator B) (...) Best regards, Juan Manuel
next prev parent reply other threads:[~2021-12-23 20:28 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-23 16:11 Robert Nikander 2021-12-23 16:54 ` Max Nikulin 2021-12-23 20:27 ` Juan Manuel Macías [this message] 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 2021-12-23 21:21 Robert Nikander 2021-12-23 21:47 ` John Kitchin 2021-12-23 22:10 ` Juan Manuel Macías
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 \ --firstname.lastname@example.org \ --email@example.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).