emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Doew output to minibuffer when using babel + R and :results silent hurting working with larger data?
Date: Tue, 30 Oct 2012 02:46:27 -0500	[thread overview]
Message-ID: <CA+M2ft8sGWRe-q+gxFeQVft0KeC-bKw9YXakmLGEY4TcEo+5kg@mail.gmail.com> (raw)

I'm working with a large dataset. I try to minimize overhead by doing
some bigger data rearranging and calculations in a single block that I
execute once per session and then switch :eval to "no."

This block is set with :results silent, but I know with this option
the results are still printed to the minibuffer. Usually this isn't a
problem, but I've had some hangs with emacs and started wondering if
this could be due to Orgmode regurgitating the results. Could this be
the case? If so, could Org be made to stop this behavior?

If I accidentally type the name of a data frame in the R session
buffer, even when I use C-c C-c  to stop the print out, it still takes
quite a while to catch up and stop itself. It made me wonder if trying
to print all of those results is increasing my compilation times

Thanks for any thoughts,

                 reply	other threads:[~2012-10-30  7:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  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=CA+M2ft8sGWRe-q+gxFeQVft0KeC-bKw9YXakmLGEY4TcEo+5kg@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).