emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Rasmus <rasmus.pank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Continuation of main section text after subsections ?
Date: Wed, 30 Mar 2011 21:41:40 -0400	[thread overview]
Message-ID: <87bp0svzfv.fsf@fastmail.fm> (raw)
In-Reply-To: <imuv8e$m8h$1@dough.gmane.org> (Rasmus's message of "Wed, 30 Mar 2011 12:05:56 +0200")

Rasmus <rasmus.pank@gmail.com> writes:

>> --8<---------------cut here---------------start------------->8---
>>  * Main headline
>>    Some thoughts expressed here
>>
>>  ** Subheading 1
>>     More thoughts expressed here
>>  ** Subheading 2
>>     More thoughts expressed here
>>  ** Main headline (cont.)
>>
>>   I would like to have this text part of 'Main headline', not of
>>   'Subheading 2'
>> --8<---------------cut here---------------end--------------->8---
>
> I don't understand the logic in this. 
>

There is no logic in it. ;) It is simply a hack to prevent the text at
the bottom from being folded into "Subheading 2". If anything, it
illustrates that terminating sub-entries in this way only has meaning
when drafting a paper, not when publishing/exporting it. Presumably one
would remove the "Main headline (cont.)" heading when exporting the
piece.

AFAICT, the OP is chiefly concerned about visibility when drafting --
i.e., he does not want all the text following "Subheading 2" be folded
into that subheading. As pointed out by others in the thread, there is
no way for html or LaTeX export to display the sort of nested logic the
OP requests.

Books and articles have the same logic as outlines; sections are only
terminated by another section of an equal or higher level. I think it is
natural that org-mode (an outlining tool) adheres to this logic, even if
it means that terminated, nested subsections (à la xml) are not
possible.

> I do however, strongly support the idea of terminating headings, but for
> other reasons. 
>
> My problem is ending * COMMENT headings. 
>
> This sketch the issue (in terms of LaTeX export):
> #+begin_src emacs-org
> * COMMENT This is were I put all my export settings, various notes and such
>
>   it could be placed as the very last headline, but that is somewhat
>   annoying an illogical to me. 
>

Moving it to the end of the outline would indeed solve these problems.
But I believe it could still be the first headline. One solution would
be to move any text prior to the first section above *all* the headlines
(including the COMMENT headline).

If you prefer, you could create a "pre-section" headline and remove it,
but not its contents, via an export hook.

Best,
Matt

  parent reply	other threads:[~2011-03-31  1:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27 15:02 Continuation of main section text after subsections ? Marcel van der Boom
2011-03-27 15:37 ` Jambunathan K
2011-03-27 15:52   ` Cian
2011-03-27 16:11     ` Marcel van der Boom
2011-03-27 16:34       ` William Gardella
2011-03-27 16:45       ` Nick Dokos
2011-03-27 17:00         ` Thomas S. Dye
2011-03-27 16:49       ` Filippo A. Salustri
2011-03-27 17:08         ` Nicolas
2011-03-27 17:10           ` Filippo A. Salustri
2011-03-27 17:02       ` William Gardella
2011-03-27 17:08         ` Filippo A. Salustri
2011-03-27 17:18           ` William Gardella
2011-03-27 17:20             ` Filippo A. Salustri
2011-03-27 20:21             ` Achim Gratz
2011-03-27 21:26               ` William Gardella
2011-03-29 18:59             ` Matt Lundin
2011-03-30  6:26               ` Aankhen
2011-03-28 14:54           ` Marcel van der Boom
2011-03-27 18:24         ` Aankhen
2011-03-27 19:29           ` Samuel Wales
2011-03-27 19:48       ` Cian
2011-03-28  0:00 ` FAQ? (was: Continuation of main section text after subsections ?) Memnon Anon
2011-03-28  8:36   ` Marcel van der Boom
2011-07-02 12:18     ` FAQ? Bastien
2011-03-29 18:54 ` Continuation of main section text after subsections ? Matt Lundin
2011-03-30 10:05   ` Rasmus
2011-03-30 11:06     ` Filippo A. Salustri
2011-03-31  1:41     ` Matt Lundin [this message]
2011-03-31  3:25       ` Samuel Wales
2011-03-31  3:26         ` Samuel Wales
2011-03-31  3:31         ` Samuel Wales
2011-03-31 20:04         ` Matt Lundin
2011-03-31 22:14           ` Aankhen
2011-03-30 18:26 ` Mark Elston
  -- strict thread matches above, loose matches on Subject: below --
2011-03-27 17:01 Rustom Mody

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=87bp0svzfv.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus.pank@gmail.com \
    /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).