From: Greg Tucker-Kellogg <gtuckerkellogg@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: specifying the coding language resulting from a a :results code source block
Date: Wed, 27 Jun 2012 12:20:16 +0800 [thread overview]
Message-ID: <5FCE8CEA-0D40-494C-9185-031330C93111@gmail.com> (raw)
In-Reply-To: <m14npxv6i8.fsf@tsdye.com>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
Mahalo Tom,
It looks like that's what I'll be doing for the ruby block. That said, it would be great if the :results code argument would allow a language specification.
Greg
On Jun 27, 2012, at 10:22 AM, Thomas S. Dye wrote:
> Greg Tucker-Kellogg <gtuckerkellogg@gmail.com> writes:
>
>> I have a Ruby block that creates some dot code. I'd like to be able
>> to have the #+RESULTS block enclosed
>> in a src block that starts "#+BEGIN_SRC dot". Using :results value
>> code generates the enclosing SRC block,
>> but using the same language (Ruby) used to generate the code. Is
>> there a way to specify the coding language
>> of a generated #+RESULTS src block?
>>
>> Thanks,
>>
>> Greg
>>
> Aloha Greg,
>
> This works for me with an emacs-lisp code block named harris-matrix that
> generates dot code.
>
> #+header: :var input=harris-matrix
> #+header: :file temp.pdf
> #+header: :cmdline -Tpdf
> #+header: :results output
> #+BEGIN_SRC dot
> $input
> #+END_SRC
>
> It's not quite what you were after, but it might help?
>
> All the best,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2012-06-27 4:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 1:08 specifying the coding language resulting from a a :results code source block Greg Tucker-Kellogg
2012-06-27 2:22 ` Thomas S. Dye
2012-06-27 4:20 ` Greg Tucker-Kellogg [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-11 9:11 Dror Atariah
2014-09-11 18:19 ` Ista Zahn
2014-09-12 7:27 ` Dror Atariah
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=5FCE8CEA-0D40-494C-9185-031330C93111@gmail.com \
--to=gtuckerkellogg@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).