In current R devel (r76247), "See Also" section of help page on
'txtProgressBar'
(https://svn.r-project.org/R/trunk/src/library/utils/man/txtProgressBar.Rd) has
"Unix-alike platforms" as a detail on 'tkProgressBar':
\seealso{
\code{\link{winProgressBar}} (Windows only),
\code{\link{tkProgres
As Tomas pointed out, it may be helpful to read the R documentation. The error
option expects a function, so I suppose you intended something like
options(error=function() {recover(); q(status=1)})
which corresponds to calling dump.frames()
Cheers,
Simon
> On Mar 17, 2019, at 23:44, comic fans
Thanks for explanation, so recover in non-interactive session exit
with 0 is expected behavior .
dump.frames said that it always write to file (workspace , or specified file).
I have a R script run as a auto build stage, so I want to print detail
backtrace to console
(with source file, line numbe
I hope you don’t mind us using this mailing list for a small
advertisement, but we think it is most relevant for this group:
We'd like to invite you to RIOT 2019 - the 4rd workshop on R
Implementation, Optimization and Tooling [1].
It will take place co-located with, and during, useR! 2019 in
As the topic came up on R-help
(as side issue in 'density vs. mass for discrete probability functions')
and Rui mentioned this old thread:
https://stat.ethz.ch/pipermail/r-help/2019-March/461989.html
I'm taking up this 5.5 years old thread from R-devel:
> peter dalgaard
> on Sat
