From: Rainer M Krug <Rainer@krugs.de>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Creating new org headers from code blocks
Date: Fri, 19 Sep 2014 14:55:32 +0200 [thread overview]
Message-ID: <m28ulfg46z.fsf@krugs.de> (raw)
In-Reply-To: <87r3z7aii2.fsf@gmail.com> (Thorsten Jolitz's message of "Fri, 19 Sep 2014 14:43:01 +0200")
[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]
Thorsten Jolitz <tjolitz@gmail.com> writes:
> Rainer M Krug <Rainer@krugs.de> writes:
>
>> Thorsten Jolitz <tjolitz@gmail.com> writes:
>> I don't quite understand your code below and what it is supposed to do.
>
> Drawers are probably better in most cases, but this code lets you use
> ':results pp replace' while developing, but converts the fixed-width pp
> results into raw results when desired (e.g. in a buffer copy before some
> action is taken).
OK - I see. But what is the advantage in this approach? Drawer do
perfectly what I want, i.e. encapsulating an org structure in a for
replacement when re-calculated, inside the drawer they behave like
normal org structure (folding, ...) and upon export they are exported as
org code would be - or am I missing something?
Rainer
>
>>> #+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
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2014-09-19 12:55 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
2014-09-19 12:15 ` Rainer M Krug
2014-09-19 12:43 ` Thorsten Jolitz
2014-09-19 12:55 ` Rainer M Krug [this message]
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=m28ulfg46z.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
--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 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).