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 03:30:09 +0200 [thread overview]
Message-ID: <87simtsrmm.fsf@gmail.com> (raw)
In-Reply-To: m238et4xi4.fsf@tsdye.com
tsd@tsdye.com (Thomas S. Dye) writes:
Hi Thomas,
> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> Hi List,
>>
>> with this org file
>>
>> ,----
>> | #+name: project-name
>> | #+header: :exports none
>> | #+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()
>> | some text
>> |
>> | * Sourcedir
>> | more text
>> `----
>>
>> I get this when exporting to ascii (excerpt):
>>
>> ,----
>> | Table of Contents
>> | _________________
>> |
>> | 1 `Testdir'
>> | 2 Sourcedir
>> |
>> |
>> | 1 `Testdir'
>> | ===========
>> |
>> | some text
>> |
>> |
>> | 2 Sourcedir
>> | ===========
>> |
>> | more text
>> `----
>>
>> and this when exporting to latex (excerpt):
>>
>> ,----
>> | \section{\texttt{Testdir}}
>> | \label{sec-1}
>> | some text
>> |
>> | \section{Sourcedir}
>> | \label{sec-2}
>> | more text
>> `----
>>
>> How do I achieve that the string returned by the src-block call is
>> treated just like normal text?
>>
>> I tried using (format ...) as well as several :results options, even
>> (intern ...), but to no avail.
>
> Here :results raw achieves what I think you want.
Unfortunately not, I tried that before, and now again, same outpout as
shown above. Did it work for you?
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-06-25 1:35 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 [this message]
2014-06-25 2:30 ` Thomas S. Dye
2014-06-25 3:01 ` Thorsten Jolitz
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=87simtsrmm.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).