emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcel van der Boom <marcel@hsdev.com>
To: "Filippo A. Salustri" <salustri@ryerson.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Continuation of main section text after subsections ?
Date: Mon, 28 Mar 2011 16:54:16 +0200	[thread overview]
Message-ID: <20110328165416.1b8357bb@hsdev.com> (raw)
In-Reply-To: <AANLkTikiGw2TwEff+t9UvTNN=UVciRDktvLw5w3S-zFm@mail.gmail.com>


On zo 27-mrt-2011 13:08
"Filippo A. Salustri" <salustri@ryerson.ca> wrote:

> I would humbly suggest that the real question is a design / use case
> question.  Is it reasonable to expect authors to stick to proper
> outline format throughout their drafting process?  If it is, then org
> is fine as is.  If it isn't, then there's a problem.

Very much agreed. I think that paragraph is the best summary so
far for the problem, stated in generic terms. 

marcel

PS
For what it is worth, I think the 'case of inline tasks' is exactly the
same problem as mine.

-- 
Marcel van der Boom  -- http://hsdev.com/mvdb.vcf
HS-Development BV    -- http://www.hsdev.com
So! web applications -- http://make-it-so.info
Cobra build          -- http://cobra.mrblog.nl

  parent reply	other threads:[~2011-03-28 14:54 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
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 [this message]
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=20110328165416.1b8357bb@hsdev.com \
    --to=marcel@hsdev.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=salustri@ryerson.ca \
    /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).