Ah, *now* we're getting somewhere. There is something that *can* be done that's genuinely helpful. >From the R(1) manual page: -q, --quiet Don't print startup message
--silent Same as --quiet --slave Make R run as quietly as possible It might have been better to use --nobanner instead of --quiet. So perhaps -q, --quiet Don't print the startup message. This is the only output that is suppressed. --silent Same as --quiet. Suppress the startup message only. --slave Make R run as quietly as possible. This is for use when running R as a subordinate process. See "Introduction to Sub-Processes in R" https://cran.r-project.org/web/packages/subprocess/vignettes/intro.html for an example. On Sat, 21 Sep 2019 at 02:29, Stephen Ellison <s.elli...@lgcgroup.com> wrote: > > > Sure, it's a silly example, but it makes about as much sense as using > > "slave" to mean "quiet". > It doesn't. It's a set of options chosen for when R is called as a slave > process from a controlling process, and in that it is a reasonable > description of the circumstance. > > --quiet is a separate command line option with different effect. > > > > > ******************************************************************* > This email and any attachments are confidential. Any u...{{dropped:13}} ______________________________________________ R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.