emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Creating new org headers from code blocks
Date: Fri, 19 Sep 2014 13:45:34 +0200	[thread overview]
Message-ID: <87zjdval5t.fsf@gmail.com> (raw)
In-Reply-To: m21tr8j58p.fsf@krugs.de

Rainer M Krug <Rainer@krugs.de> writes:

Hi,

> I have some R code which generates several graphics. I would now like to
> generate in R text which is then interpreted by org, upon export, as
> normal org code. Furthermore, I would like to create new org headers from
> the R code. Imagine I have the R code block below. Executed, I get the
> results below:
>
> --8<---------------cut here---------------start------------->8---
> * Some code block
> #+begin_src R :results raw :wrap :exports both
> c("** New header", "[[./graph1.pdf]]", "", "** and second header", "and some text" )
> #+end_src
>
> #+RESULTS:
> #+BEGIN_RESULTS
> ,** New header
> [[./graph1.pdf]]
>
> ,** and second header
> and some text
> #+END_RESULTS
> --8<---------------cut here---------------end--------------->8---
>
> I can leave the :wrap, but then the results are not overwritten, but
> appended - otherwise it works as expected.
>
> How can I achieve that I get 
>
> ,----
> | ** New header
> | [[./graph1.pdf]]
> | 
> | ** and second header
> | and some text
> `----
>
> in the org file, but also that the result gets overwritten upon repeated
> execution?

I asked about this ':results raw' limitation before and was told to RTFM
;)

(although its not really on the page where I would look for it:
http://orgmode.org/manual/results.html).

You could look-up that thread in the mailing-list for some tips, and/or
use this on a temporary buffer-copy just before you want to act on the
raw results:

#+BEGIN_SRC emacs-lisp :results none
  (defvar tj/fixed-width-to-raw-langs '("R")
    "List of Babel langs for `tj/fixed-width-to-raw-results'.")

  (defun tj/fixed-width-to-raw-results ()
    "Call `org-toggle-fixed-width' on ':results pp'."
    (org-babel-map-src-blocks nil
      (and (member lang tj/toggle-fixed-width-src-block-langs)
           (member "pp" (split-string header-args " " t))
           (save-excursion
             (goto-char (org-babel-where-is-src-block-result))
             (forward-line)
             (while (org-in-fixed-width-region-p)
               (org-toggle-fixed-width)
               (forward-line))))))

#+END_SRC

#+begin_src R :results pp replace
 c("** New header2", "[[./graph1.pdf]]", "", "** and second header", "and some text" )
#+end_src

#+results:
: ** New header2
: [[./graph1.pdf]]
: 
: ** and second header
: and some text

-- 
cheers,
Thorsten

next prev parent reply	other threads:[~2014-09-19 11:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 10:04 Creating new org headers from code blocks Rainer M Krug
2014-09-19 11:45 ` Thorsten Jolitz [this message]
2014-09-19 12:15   ` Rainer M Krug
2014-09-19 12:43     ` Thorsten Jolitz
2014-09-19 12:55       ` Rainer M Krug
2014-09-19 13:32         ` Thorsten Jolitz
2014-09-19 13:40           ` Rainer M Krug

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=87zjdval5t.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

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).