emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: Aaron Ecay <aaronecay@gmail.com>
Cc: Daniele Pizzolli <dan@toel.it>,
	org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Evaluating R source code line by line
Date: Tue, 16 Dec 2014 04:28:20 +0530	[thread overview]
Message-ID: <900A5E3A-BF49-4A49-90D9-25DBA1C8B181@agrarianresearch.org> (raw)
In-Reply-To: <87vblf2vdd.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 318 bytes --]

> For your use case, I would suggest adding print() calls in strategic
> places in your long-running code, which will appear in the R buffer to
> let you know how it’s progressing.

I don’t quite understand everything you wrote. But this would be helpful for my test case. Will use.



[-- Attachment #2: Type: text/html, Size: 1250 bytes --]

  reply	other threads:[~2014-12-15 22:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13  2:26 Evaluating R source code line by line Vikas Rawal
2014-12-13 10:12 ` Daniele Pizzolli
2014-12-13 13:18   ` Vikas Rawal
2014-12-13 19:38     ` Aaron Ecay
2014-12-15 22:58       ` Vikas Rawal [this message]
2014-12-16 16:32         ` Andreas Leha
2014-12-16 18:43           ` Andreas Leha

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=900A5E3A-BF49-4A49-90D9-25DBA1C8B181@agrarianresearch.org \
    --to=vikaslists@agrarianresearch.org \
    --cc=aaronecay@gmail.com \
    --cc=dan@toel.it \
    --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).