From: "Eric Schulte" <schulte.eric@gmail.com>
To: Leo Alekseyev <dnquark@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-babel, R, and org-babel-open-src-block-result
Date: Tue, 11 Jan 2011 09:37:28 -0700 [thread overview]
Message-ID: <87bp3nxsdn.fsf@gmail.com> (raw)
In-Reply-To: AANLkTin7FR+4cY2xFHyAVdgoqZVmr-E=9vRanUPAjoRj@mail.gmail.com
Leo Alekseyev <dnquark@gmail.com> writes:
> I recently started using org-babel with R, and so far I think it's
> pretty great! I'm still getting accustomed to org-babel workflow and
> am playing with available options. I have a couple of questions:
>
> I noticed that C-c C-o (org-babel-open-src-block-result) always gives
> me an empty *Org-Babel Results* buffer, even if there's output printed
> to #+results section. Is this a bug? Am I doing something wrong?
>
I have not noticed this myself, can you share an example?
>
> On a similar note, is there an option for the #+ results session to be
> completely suppressed?.. I can see situations where I might simply
> want to send the code to the inferior process and examine the results
> there using :results output :session, or perhaps I'm running the code
> just for the side effects. It would be nice if I could say e.g.
> :results none.
>
Yes, for a complete list of the available header arguments and their
effects please see
http://orgmode.org/manual/Working-With-Source-Code.html
>
> Thanks and keep up the good work with org-babel!
>
> --Leo
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2011-01-11 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 10:22 org-babel, R, and org-babel-open-src-block-result Leo Alekseyev
2011-01-11 14:55 ` Erik Iverson
2011-01-11 16:54 ` Leo Alekseyev
2011-01-11 17:44 ` Eric Schulte
2011-01-11 16:37 ` Eric Schulte [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=87bp3nxsdn.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=dnquark@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).