From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Possible to use src block to generate org headlines for export?
Date: Fri, 25 Jul 2014 14:39:15 +0100 [thread overview]
Message-ID: <olu38dpimm4.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87zjfxk1wb.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>
>> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>>> No matter how special the results drawer is, it cannot (and shouldn't)
>>> contain headlines.
>>
>> You are the master of the parser...
>
> That's why I carefully avoid shooting myself in the foot. There is (at
> least) a good reason why only headlines can contain headlines, which is
> speed, as a consequence of CFG.
>
>> IIUC, you are saying that raw+replace is possible right now for any
>> content in the results (other than headlines), if the results are in a
>> drawer?
>
> If the results are in a drawer, this is not "raw" anymore, but "drawer".
> Anyway you can put anything in your drawer besides a headline and
> another drawer.
But then, I do not understand your statement 'headlines are the only
limitation to raw+replace behaviour'.
This code block does not seem to respect 'raw+replace' for me:
#+name: dtrn
#+BEGIN_SRC R :results raw replace
nwords <- 500
nletters <- sapply(1:nwords, function(i) sample(1:10, 1))
words <- sapply(nletters, function(i) paste(sample(letters, i), collapse=""))
words[sample(nwords, 100)] <- "\n"
paste(words, collapse=" ")
#+END_SRC
>
>> Then, my follow-up question is simply, why are drawers not the default
>> for results, then? Is there any drawback (apart from an additional
>> line)?
>
> The block may insert a headline, or another drawer, within the results
> drawer, thus breaking the document.
>
I understand that. Will update my local 'defaults' then to drawer.
Regards,
Andreas
next prev parent reply other threads:[~2014-07-25 13:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 23:52 Possible to use src block to generate org headlines for export? Matt Lundin
2014-07-23 1:27 ` Nick Dokos
2014-07-23 2:35 ` Matt Lundin
2014-07-23 2:46 ` Matt Lundin
2014-07-23 13:42 ` Brett Viren
2014-07-23 15:17 ` Matt Lundin
2014-07-23 16:06 ` Charles Berry
2014-07-23 17:07 ` Matt Lundin
2014-07-24 1:51 ` Nick Dokos
2014-07-24 10:21 ` Andreas Leha
2014-07-25 8:31 ` Nicolas Goaziou
2014-07-25 13:05 ` Andreas Leha
2014-07-25 13:23 ` Nicolas Goaziou
2014-07-25 13:39 ` Andreas Leha [this message]
2014-07-25 14:26 ` Thorsten Jolitz
2014-07-25 16:08 ` Nicolas Goaziou
2014-07-26 0:26 ` Andreas Leha
2014-07-26 8:07 ` Nicolas Goaziou
2014-07-26 19:47 ` Andreas Leha
2014-07-24 18:40 ` Charles Berry
2014-07-24 19:41 ` Nick Dokos
2014-07-23 19:53 ` Brett Viren
2014-07-23 20:42 ` Matt Lundin
2014-07-24 22:05 ` Brett Viren
2014-07-23 16:09 ` Rick Frankel
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=olu38dpimm4.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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).