Full_Name: Peter Perkins
Version: 1.2.1
OS: LinuxPPC
Submission from: (NULL) (24.4.89.36)
Unlike (at least some) other args/components of ps.options(), the onefilearg to
postscript() does not default to ps.options()$onefile. For the familyand
landscape= args, for example, it does. Looking at postscript()'s code,
this
appears to be intentional. If it _is_ intentional, the following clarification
might be added to the "onefile" line of the arguments section of the
postscript/ps.options help:
"the onefile= arg to postscript() does _not_ default to the value set
in the most recent call to ps.options(); rather, it defaults to TRUE."
but this raises the question, "just where _is_ the onefile arg to
ps.options()
used, if not by postscript()?"
if the current behavior is not correct, then the solution seems to be
to change the default value to .PostScript.Options$onefile, if that's not
too ugly. leaving onefile= out of the arg list would work, except then
the file= arg is left hanging. for what it's worth, the explicit familyarg
seems to be superfluous, it would be handled by ... and the call to
check.options().
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !) To:
r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._