emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Samuel Wales <samologist@gmail.com>
Cc: Memnon Anon <gegendosenfleisch@googlemail.com>,
	nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Continuation of main section text after subsections
Date: Mon, 28 Mar 2011 10:42:56 -0400	[thread overview]
Message-ID: <31082.1301323376@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Samuel Wales <samologist@gmail.com> of "Sun, 27 Mar 2011 18:07:04 PDT." <AANLkTi=OEFWZuvrcO0btH0iymhO-GcyaZvHRyRe-o2nC@mail.gmail.com>

Samuel Wales <samologist@gmail.com> wrote:

> Perhaps we could have a tag like :noexport: except that it exports
> body.  It does not export the header.  Optionally, it would be
> replaced with a blank line.
> 
> Then he can put headers anywhere he wants.
> 
> Would this work for the OP's use case?
> 

My reading of it was that he wanted that to be done as he is putting
down his thoughts into the pensieve - ...err... org file I mean - so doing
it in export is too late. But I'm not the OP so maybe I've read it
wrong.

Using an imaginary EBNF spec, here's what org (and LaTeX) provides:

<tree> ::= [<text>] (<tree>)*

i.e. "a tree is some optional text followed by 0 or more trees",
whereas I think he wants:

<tree> ::= [<text>] (<tree> [text])*

I hope these are not grossly wrong, but please take them with
the appropriate grain of salt.

Nick

  parent reply	other threads:[~2011-03-28 14:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28  1:07 Continuation of main section text after subsections Samuel Wales
2011-03-28  4:18 ` Thomas S. Dye
2011-03-28  7:09 ` Sébastien Vauban
2011-04-18 15:34   ` Colin Fraizer
2011-04-18 16:17     ` Marcel van der Boom
2011-04-18 16:42       ` Colin Fraizer
2011-04-18 18:32         ` Jeff Horn
2011-03-28 14:42 ` Nick Dokos [this message]
2011-03-28 14:50 ` Marcel van der Boom
  -- strict thread matches above, loose matches on Subject: below --
2011-04-26  0:02 Skip Collins

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=31082.1301323376@alphaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gegendosenfleisch@googlemail.com \
    --cc=samologist@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).