From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Controlling example block export?
Date: Tue, 01 Apr 2014 12:10:12 +0200 [thread overview]
Message-ID: <87k3b9mkcb.fsf@gmail.com> (raw)
In-Reply-To: CAK=ukcYqOcSDCudX3Yez7tgsv8fBgRVtHkoRGpGr8MZB96bDYA@mail.gmail.com
Heikki Lehvaslaiho <heikki.lehvaslaiho@gmail.com> writes:
> I am using example blocks as inline notes where I paste snippets of
> (pre-formatted) text. I'd like to be able to control the exporting of
> those block individually (per document would also be useful). I do not
> seem to be able to find documentation about anything along those
> lines.
>
> Here is a mock-up:
>
> #+BEGIN_EXAMPLE :exports none
> private notes...
> #+END_EXAMPLE
I don't think example blocks take arguments. You might try
#+BEGIN_SRC org :exports none
private notes...
#+END_SRC
or collect these example blocks in subtrees with export tags/properties.
> A bigger question is that while code blocks are well defined and well
> documented, all other blocks are not. Is there somewhere a design
> document the would give a logic of having different blocks and how
> they are controlled? Maybe there is an other type of a block that does
> what I want?
> The inline documentation in ox*.el files is too low level to be
> helpful.
AFAIK export of these block types is backend specific, e.g. ox-ascii.el
might treat example block different than ox-html.el, so thats where to
look.
,---------------------------
| C-h v org-export-with- TAB
`---------------------------
gives some hints too. Using drawers instead of example blocks would
enable you to toggle export documentwise.
I asked a similar 'bigger' question before, and remember that the answer
was more or less 'the block name says it all'.
However, here is a (dense) description of the org syntax:
,--------------------------------------------
| http://orgmode.org/worg/dev/org-syntax.html
`--------------------------------------------
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-04-01 10:09 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 [this message]
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
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
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=87k3b9mkcb.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).