emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: How to treat string results of src-block calls like text in export?
Date: Wed, 25 Jun 2014 05:01:27 +0200	[thread overview]
Message-ID: <87simt1ym0.fsf@gmail.com> (raw)
In-Reply-To: m21tud67r2.fsf@tsdye.com

tsd@tsdye.com (Thomas S. Dye) writes:

Hi Thomas,

> I use this a lot in my work, but hadn't tried it in a headline.  I tried
> it with the call line in a headline and that works, too.  This subtree
> is in a file called personal.org.
>
> * Jolitz
>
> #+name: project-name
> #+header: :exports none :results raw
> #+begin_src emacs-lisp
>   (mapconcat
>    'capitalize
>    (split-string
>     (file-name-nondirectory
>      (directory-file-name
>       (file-name-directory
>        (buffer-file-name (current-buffer)))))
>     "-" 'OMIT-NULLS)
>    " ")
> #+end_src
>
> ** call_project-name()[:results raw]
>
> ** Impersonal
>
> The LaTeX export looks like this, in part:
>
> \section{Personal}
> \label{sec-1}
>
> \section{Impersonal}
> \label{sec-2}
> % Emacs 24.3.1 (Org mode beta_8.3)
>
> Alternatively, you can put :results raw in a header-args property of the
> subtree and then just call_project-name().

,----
| ** call_project-name()[:results raw]
`----

Thats it, I used :results raw for the called block, not for the caller
(like in <end header arguments>), now it works like a charm.

Thanks!

-- 
cheers,
Thorsten

      reply	other threads:[~2014-06-25  3:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  0:00 How to treat string results of src-block calls like text in export? Thorsten Jolitz
2014-06-25  0:57 ` Thomas S. Dye
2014-06-25  1:30   ` Thorsten Jolitz
2014-06-25  2:30     ` Thomas S. Dye
2014-06-25  3:01       ` Thorsten Jolitz [this message]

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=87simt1ym0.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).