But in that case let me return to and refine my proposal: Why not have
drawer as the default unless raw is given?
Probably because raw never breaks your document, and is less verbose
in the simplest cases (e.g., a single list, value, table...), which may
be common enough.
Anyway, it should be
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
But in that case let me return to and refine my proposal: Why not have
drawer as the default unless raw is given?
Probably because raw never breaks your document, and is less verbose
in the simplest cases (e.g., a single list, value, table...),
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Is that a valid feature request:
Allow the combination of :results raw and :results replace -- regardless
of the produced content?
IIUC the parser does not allow this right now. But (without any
knowledge on the parser) I can
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Is that a valid feature request:
Allow the combination of :results raw and :results replace -- regardless
of the produced content?
IIUC the parser does not allow
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Nicolas Goaziou m...@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.
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Nicolas Goaziou m...@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
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
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
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
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
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
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
Hi all,
Nick Dokos ndo...@gmail.com writes:
Charles Berry ccbe...@ucsd.edu writes:
Matt Lundin mdl at imapmail.org writes:
[deleted]
Footnotes:
[fn:1] If one really needs to see the headlines in the original org
buffer, a hook can be used to remove the :RESULTS: drawer.
Nick Dokos ndokos at gmail.com writes:
Charles Berry ccberry at ucsd.edu writes:
Matt Lundin mdl at imapmail.org writes:
[deleted]
[more deleted]
Or wrap the results in a drawer when you type C-c C-c, but render them as
raw on export (which removes the drawer and replaces with
Charles Berry ccbe...@ucsd.edu writes:
Nick Dokos ndokos at gmail.com writes:
Charles Berry ccberry at ucsd.edu writes:
Matt Lundin mdl at imapmail.org writes:
[deleted]
[more deleted]
Or wrap the results in a drawer when you type C-c C-c, but render them as
raw on export
Matt Lundin m...@imapmail.org writes:
That sounds interesting. I look forward to hearing more!
It's not yet usable for anything real but I'm keeping the work here:
https://github.com/brettviren/orgonpy
-Brett.
pgptNgTBz8D6F.pgp
Description: PGP signature
Matt Lundin m...@imapmail.org writes:
Let's hope the real blog (when I get around to publishing it) is more
interesting than the example above. ;)
Maybe it would be more convenient to add the meta-ness you want as
part of a new exporter process?
-Brett.
pgpX0dUH7NC9P.pgp
Description: PGP
Hi Brett,
Brett Viren b...@bnl.gov writes:
Matt Lundin m...@imapmail.org writes:
Let's hope the real blog (when I get around to publishing it) is more
interesting than the example above. ;)
Maybe it would be more convenient to add the meta-ness you want as
part of a new exporter process?
Matt Lundin mdl at imapmail.org writes:
[deleted]
Footnotes:
[fn:1] If one really needs to see the headlines in the original org
buffer, a hook can be used to remove the :RESULTS: drawer.
--8---cut here---start-8---
(defun
On 2014-07-22 22:35, Matt Lundin wrote:
Nick Dokos ndo...@gmail.com writes:
In short, is there a more graceful and export-friendly way to use babel
to generate org headlines for export? Or is there an easy way to get
the
export backend to delete the opening part of the drawer (i.e.,
Charles Berry ccbe...@ucsd.edu writes:
Matt Lundin mdl at imapmail.org writes:
Or wrap the results in a drawer when you type C-c C-c, but render them as
raw on export (which removes the drawer and replaces with raw results).
Like so:
#+header: :results (if (boundp 'backend) raw drawer)
Matt Lundin m...@imapmail.org writes:
Brett Viren b...@bnl.gov writes:
Maybe it would be more convenient to add the meta-ness you want as
part of a new exporter process?
To change the meta wrappers for code block results, we would have to
modify org babel (ob-core.el).
Just to be clear
Brett Viren b...@bnl.gov writes:
Matt Lundin m...@imapmail.org writes:
Brett Viren b...@bnl.gov writes:
Maybe it would be more convenient to add the meta-ness you want as
part of a new exporter process?
To change the meta wrappers for code block results, we would have to
modify org
Charles Berry ccbe...@ucsd.edu writes:
Matt Lundin mdl at imapmail.org writes:
[deleted]
Footnotes:
[fn:1] If one really needs to see the headlines in the original org
buffer, a hook can be used to remove the :RESULTS: drawer.
--8---cut
I am attempting to use a babel code snippet to generate org headlines
for export. However, I seem to be running into a corner case here.
AFAICT, the only way to generate headlines safely with babel is to wrap
them in a :RESULTS: drawer.
Take the following example:
--8---cut
Matt Lundin m...@imapmail.org writes:
I am attempting to use a babel code snippet to generate org headlines
for export. However, I seem to be running into a corner case here.
AFAICT, the only way to generate headlines safely with babel is to wrap
them in a :RESULTS: drawer.
Take the
Nick Dokos ndo...@gmail.com writes:
In short, is there a more graceful and export-friendly way to use babel
to generate org headlines for export? Or is there an easy way to get the
export backend to delete the opening part of the drawer (i.e.,
:RESULTS:)?
Any advice would be greatly
Correction below...
Matt Lundin m...@imapmail.org writes:
#+BEGIN_SRC emacs-lisp :exports none :results none
(save-excursion
(goto-char (point-min))
(while (re-search-forward #\\+RESULTS: generate-blog-summary nil t)
(when ...
(beginning-of-line)
(delete-region
25 matches
Mail list logo
