From: Johan Sandblom <jsandblom@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Removing banner from mtxrun output
Date: Mon, 20 Sep 2010 22:02:22 +0200 [thread overview]
Message-ID: <AANLkTinQ4APvVx++LXxKgwujafnmSpFoG=MoQr9=QjSc@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1009200505300.13138@ybpnyubfg.ybpnyqbznva>
2010/9/20 Aditya Mahajan <adityam@umich.edu>:
> On Mon, 20 Sep 2010, Johan Sandblom wrote:
> Why are you using input output redirection
>
> R .... < \Rfile\space > \Rfile.out
>
> rather than a simple
>
> R .... \Rfile\space \Rfile.out
Originally, I think it was because it was the only way that worked on
both Windows and Linux, but lately it is because R CMD BATCH produces
produces a couple of lines of processing times at the end, which I do
not want.
> @Hans, mtxrun be completely silent when used to launch external programs and
> only give some output if --verbose is passed.
That would make more sense.
> BTW, there is a serious bug in the R module: each code chunck carries a
> state with it (--save --restore), but this state can depend on which chunck
> was changed.
Indeed. But I have learned to live with it.
> This "bug" can be avoided by doing some book keeping for the external state
> (saving the file to a different name and restoring it), or by not using
> --save and --restore.
Yes. But the book keeping gets a little complicated and ugly since it
needs to be done from within R (--save takes no arguments). Or
possibly all chunks after an altered chunk should be run.
Thanks for your comments, Johan
> Aditya
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
--
Johan Sandblom, MD PhD
m +46735521477 Sweden
"What is wanted is not the will to believe, but the
will to find out, which is the exact opposite"
- Bertrand Russell
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2010-09-20 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 8:26 Johan Sandblom
2010-09-20 8:44 ` luigi scarso
2010-09-20 9:23 ` Aditya Mahajan
2010-09-20 20:56 ` Johan Sandblom
2010-09-21 18:44 ` Johan Sandblom
2010-09-21 19:28 ` Peter Münster
2010-09-21 20:18 ` Aditya Mahajan
2010-09-21 20:37 ` Johan Sandblom
2010-09-21 20:45 ` Hans Hagen
2010-09-20 9:17 ` Aditya Mahajan
2010-09-20 20:02 ` Johan Sandblom [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTinQ4APvVx++LXxKgwujafnmSpFoG=MoQr9=QjSc@mail.gmail.com' \
--to=jsandblom@gmail.com \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).