From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Heikki Lehvaslaiho <heikki.lehvaslaiho@gmail.com>
Cc: emacs-orgmode@gnu.org, Thorsten Jolitz <tjolitz@gmail.com>
Subject: Re: Controlling example block export?
Date: Tue, 01 Apr 2014 17:38:15 +0200 [thread overview]
Message-ID: <87k3b9njq0.fsf@gmail.com> (raw)
In-Reply-To: <CAK=ukca7cyZEG=VTDUQNfUQ5ESkrVjPS398r230deWpDhRP=XA@mail.gmail.com> (Heikki Lehvaslaiho's message of "Tue, 1 Apr 2014 15:40:14 +0300")
Hello,
Heikki Lehvaslaiho <heikki.lehvaslaiho@gmail.com> writes:
> The org-syntax.html says of blocks:
>
> #+BEGIN_NAME PARAMETERS
> CONTENTS
> #+END_NAME
>
> NAME can contain any non-whitespace character.
> PARAMETERS can contain any character other than new line, and can be
> omitted.
> If NAME is "CENTER", it will be a "center block". If it is "QUOTE", it will
> be a "quote block".
> If the block is neither a center block, a quote block or a block
> element<http://orgmode.org/worg/dev/org-syntax.html#Blocks>,
> it will be a "special block".
>
> That does not seem to be quite true as lisp/org-element.el recognises the
> following blocks (perlregexp: /begin_(\w+)/i):
Have you looked at:
http://orgmode.org/worg/dev/org-syntax.html#Blocks
> Note: org-syntax.html needs updating.
Possibly. Where?
> So, to implement parameters for the EXAMPLE block, relevant code has to be
> added to the exporter. That's a nontrivial task to do consistently.
For now, there is no need for that.
> Incidentally, the solution to my immediate problem is the COMMENT block.
> Its contents are completely ignored and not passed to exporters.
This is the purpose of comments.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-04-01 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 9:20 Controlling example block export? Heikki Lehvaslaiho
2014-04-01 10:10 ` Thorsten Jolitz
2014-04-01 12:40 ` Heikki Lehvaslaiho
2014-04-01 14:52 ` Thorsten Jolitz
2014-04-01 15:16 ` Thorsten Jolitz
2014-04-01 15:38 ` Nicolas Goaziou [this message]
2014-04-01 15:34 ` Nicolas Goaziou
2014-04-01 16:33 ` Charles Berry
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3b9njq0.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=heikki.lehvaslaiho@gmail.com \
--cc=tjolitz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.