emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Marcel van der Boom <marcel@hsdev.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Re: Continuation of main section text after subsections ?
Date: Sun, 27 Mar 2011 12:45:31 -0400	[thread overview]
Message-ID: <20408.1301244331@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Marcel van der Boom <marcel@hsdev.com> of "Sun, 27 Mar 2011 18:11:55 +0200." <20110327181155.054fecf2@hsdev.com>

Marcel van der Boom <marcel@hsdev.com> wrote:

> When writing I tend to think about org headings as 'handles' to a
> logical block of information, including its child blocks. Apparently my
> analogy clashes with what org-mode wants. I had my hopes on a
> customization option. 
> 
> Is there a strong reason this could not work as an option in org-mode?
> 

I'm sure that patches would be welcome, but I think you'd find it
difficult to specify, let alone implement. In particular, how do you
tell where the section 1.1.1 stuff ends and the section 1 stuff begins
again? And would the extra stuff be part of section 1 or (sub)section
1.1? Why? And don't forget this is all just text, so any markup has to
be minimal, intuitive and as unobtrusive as possible.

The devil is in the details.

Nick

  parent reply	other threads:[~2011-03-27 16:45 UTC|newest]

Thread overview: 35+ 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 [this message]
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

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=20408.1301244331@alphaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=marcel@hsdev.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).