emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mark Elston <m_elston@comcast.net>
To: emacs-orgmode@gnu.org
Subject: Re: Continuation of main section text after subsections ?
Date: Wed, 30 Mar 2011 11:26:54 -0700	[thread overview]
Message-ID: <4D9375EE.8080704@comcast.net> (raw)
In-Reply-To: <20110327170251.58923564@hsdev.com>

On 3/27/2011 8:02 AM, Marcel van der Boom wrote:
> Hi,
>
> When I'm using orgmode to write out largish documents, I often run into
> the outlining problem that it's apparently not possible to continue
> text of a higher level outline once subsections have been started.
>
> A simplified example of such an outline would be:
>
> ---
> * Main headline
>    Some thoughts expressed here
>
> ** Subheading 1
>     More thoughts expressed here
> ** Subheading 2
>     More thoughts expressed here
>
>   I would like to have this text part of 'Main headline', not of
>   'Subheading 2'
> ----

I have been following this thread with some interest.  But I must admit
to being a little confused as to what is meant by the last sentence,
above.

If this is just a matter of indentation in the org file that can be
handled by the user.  Org will honor any user-specified indentation for
entered text and all subsequent text will maintain the same indentation
until a new heading is encountered or the user enters text with a new
indentation level.

If, OTOH, what is asked for is having org "understand" that the final
sentence was part of the main heading so that folding subheading 2 would
not fold the last sentence as well, that is something else entirely.  I
would suggest that the common rules of outlining should be observed so
as to minimize the principle of least surprise to the end user.  Org
mode is, after all, an outliner (albeit one with a /lot/ of bells and
whistles added for convenience).

On those occasions where I ran into something similar I wound up
restructuring my organization to suit.  For example, the above might be
better structured as:

* Main headline
   Some thoughts expressed here
** Initial points
*** Subheading 1
     More thoughts expressed here
*** Subheading 2
     More thoughts expressed here
** Next set of points
    I would like to have this text part of 'Main headline', not of
    'Subheading 2'.  However, as it doesn't belong to the previous
    set of points it starts a new subsection of the 'Main headline.'

etc.

This seems more in line with what you were intending, anyway.

Something to keep in mind here is that in the final output, unless you
really jump through some hoops, there isn't going to be any difference
in the text associated with the different heading levels.  That is, text
under "Main headline" will look (font/indentation/etc) identical to text
under "Subheading 1", etc.  So the only real difference is going to
come from the nature of the outline and the subsequent sectioning
commands in the output.  Of course, if "Subheading 1/2" were changed to
lists this is /not/ the case as lists are visually distinct from the
surrounding text...

I have recently been playing with Freemind and find it a pretty
interesting alternative to a purely textual listing as in org-mode.
However, mind-maps seem to be rather isomorphic with outlines in many
ways and *still* follow most of the same rules (adapted for a graphical
environment, of course).

I guess I am just not certain how "free floating" text in an outline
is to be viewed conceptually, or to be rendered in the final output.

Mark

  parent reply	other threads:[~2011-03-30 18:27 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
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 [this message]
  -- 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=4D9375EE.8080704@comcast.net \
    --to=m_elston@comcast.net \
    --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).