From: Dror Atariah <drorata@gmail.com>
To: Ista Zahn <istazahn@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: specifying the coding language resulting from a a :results code source block
Date: Fri, 12 Sep 2014 09:27:34 +0200 [thread overview]
Message-ID: <CANfRcg2d10Gtek6daxgYLFXg2SxnyiP0F9mmcWjPCDT6gqMgJw@mail.gmail.com> (raw)
In-Reply-To: <CA+vqiLF7u1s1DkOcZVAeuf+GbWDhQ2Te9DRjhGi9-3a7GYrCsA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
Indeed, this seems to do the trick!
Thanks!
On Thu, Sep 11, 2014 at 8:19 PM, Ista Zahn <istazahn@gmail.com> wrote:
> Can't you just do
>
> #+begin_src foo :wrap src bar
> hello world
> #+end_src
>
> ?
>
> Best,
> Ista
>
>
> On Thu, Sep 11, 2014 at 5:11 AM, Dror Atariah <drorata@gmail.com> wrote:
> > Is there some change in the status of this issue? Can one now specify the
> > language of the result?
> >
> > Cheers,
> > Dror
> >
> > ----------
> > 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 <address@hidden> 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: Type: text/html, Size: 2718 bytes --]
next prev parent reply other threads:[~2014-09-12 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 9:11 specifying the coding language resulting from a a :results code source block Dror Atariah
2014-09-11 18:19 ` Ista Zahn
2014-09-12 7:27 ` Dror Atariah [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-27 1:08 Greg Tucker-Kellogg
2012-06-27 2:22 ` Thomas S. Dye
2012-06-27 4:20 ` Greg Tucker-Kellogg
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=CANfRcg2d10Gtek6daxgYLFXg2SxnyiP0F9mmcWjPCDT6gqMgJw@mail.gmail.com \
--to=drorata@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=istazahn@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).