From: William Gardella <gardellawg@gmail.com>
To: Marcel van der Boom <marcel@hsdev.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Continuation of main section text after subsections ?
Date: Sun, 27 Mar 2011 12:34:29 -0400 [thread overview]
Message-ID: <878vw0froq.fsf@lw-wireless-pittnet-40-144.wireless.pitt.edu> (raw)
In-Reply-To: <20110327181155.054fecf2@hsdev.com> (Marcel van der Boom's message of "Sun, 27 Mar 2011 18:11:55 +0200")
Marcel van der Boom <marcel@hsdev.com> writes:
> On zo 27-mrt-2011 16:52
> Cian <cian.oconnor@gmail.com> wrote:
>
>> You can't do that, as it would be akin to trying to have in a book
>>
>> Section 1
>> Stuff
>> Section 1.1.1
>> More stuff
>>
>> Now this goes under Section 1
>>
>> Not really an idiom that makes sense (I find its best to think of
>> org-mode's headings as chapter headers
>
> Agreed, for paper books that would not make much sense (depending on
> how you do it) and that fact kept me from asking the question for a
> while.
> For electronic texts however, especially in the drafting stage where
> (sub-)sections get shuffled around, promoted, demoted, split etc. it
> does make sense, to me at least.
>
> 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?
>
> marcel
Marcel,
I think this is not yet easily possible in org-mode due to the
limitations of org's rather simple concept of markup. Because org tries
to stay out of the way of the user's choice of indentation flow, for
example, whitespace can't be used to indicate that your text has
returned to the top level after entering a subheading. And unlike in,
e.g., HTML or LaTeX, there's no way of "closing" the subheading
environment explicitly.
As Cian suggests, some alternatives you can use are to employ drawers or
environments such as #+BEGIN_NOTE.
I also use Org as a drafting tool, mostly for documents that will end up
as papers or legal documents rendered with LaTeX. There are a few
ambiguities in the markup that are hard to resolve without going the
additional step of exporting to HTML or LaTeX and editing that output.
You've just stumbled into one of them...
--
William Gardella
J.D. Candidate
Class of 2011, University of Pittsburgh School of Law
next prev parent reply other threads:[~2011-03-27 16:34 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 [this message]
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
-- 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=878vw0froq.fsf@lw-wireless-pittnet-40-144.wireless.pitt.edu \
--to=gardellawg@gmail.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).