From: "Eric Schulte" <schulte.eric@gmail.com>
To: Leo Alekseyev <dnquark@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: org-babel, R, and org-babel-open-src-block-result
Date: Tue, 11 Jan 2011 10:44:22 -0700 [thread overview]
Message-ID: <87hbdfwd1l.fsf@gmail.com> (raw)
In-Reply-To: <loom.20110111T174245-19@post.gmane.org> (Leo Alekseyev's message of "Tue, 11 Jan 2011 16:54:21 +0000 (UTC)")
Leo Alekseyev <dnquark@gmail.com> writes:
> Erik Iverson <eriki <at> ccbr.umn.edu> writes:
>
>>
>> On 01/11/2011 04:22 AM, Leo Alekseyev wrote:
>> > 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?
>> >
>> > 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.
>>
>> From the manual:
>>
>> The following results options indicate what happens with the results once they
>> are collected.
>>
>> * silent
>> The results will be echoed in the minibuffer but will not be inserted into the
>> Org-mode buffer. E.g., :results output silent.
>
> Thanks Erik. It would be nice if section 14.9 of the Org manual could
> reference 14.8.2.
I couldn't agree more, I've just pushed up this change to the manual.
> In general, it would be nice if the org HTML documents could support
> the same outline folding cycling behavior that you see in Emacs
> buffers, otherwise it's difficult to see the surrounding context.
>
I personally prefer to use the Emacs `info' interface, both because you
can easily text search through all parts of the manual, and for issues
of navigation and viewing a wider context.
>
> I'd still like to know what (org-babel-open-src-block-result) is
> supposed to do... Haven't found that in the manual.
>
Hmm, apparently in some cases it does nothing currently due to a bug,
I've just fixed this buy, so please pull the latest Org-mode, and try
copying the following block and results into and Org-mode buffer and
calling C-c C-o from within the code block.
#+begin_src emacs-lisp
(mapcar #'list (reverse (org-babel-src-block-names)))
#+end_src
#+results:
| tangle-A |
| tangle-C |
| i-have-a-name |
| add-column-in-table-0 |
| rec-string-wrap |
| add-col |
| a-list |
| lob-header |
| test |
| name |
| cycle |
| body |
| eight |
| org-list |
| numbers |
Cheers -- Eric
next prev parent reply other threads:[~2011-01-11 17:47 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 [this message]
2011-01-11 16:37 ` Eric Schulte
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=87hbdfwd1l.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).