On Sun, 2023-04-16 at 13:52 +0200, Iñaki Ucar wrote:
> I agree that something like this would be a nice addition. With the
> current condition system, it would be certainly easy (but quite a lot
> of work) to define a hierarchy of built-in conditions, and then use
> them consistently throughout ba
I am the author of the *tryCatchLog* package and want to
- suppress selected conditions (warnings and messages)
- rethrow selected conditions (e.g a specific warning as a message or to
"rename" the condition text).
I could not find any reliable unique identifier for each possible condition
- t
In fact an attentive user reported the same type of (slow due to deparse)
problem in may tryCatchLog package recently when using a large sparse matrix
https://github.com/aryoda/tryCatchLog/issues/68
and I have fixed it by explicitly using the nlines arg of deparse() instead of
using as.char
May be unrelated but on SO there is a report that a Windows update may cause
this problem:
https://stackoverflow.com/questions/63457321/r-will-not-run-after-latest-windows-10-updates/63524608#63524608
On Fri, 2020-08-21 at 12:34 +, m1388m+moe1ydyn0hbs--- via R-devel wrote:
> I am having ex
Dear R developers,
I am developing an R package which returns strings with new line codes.
I am not sure if I should use "\r\n" or "\n" in my returned strings on Windows
platforms.
What is the recommended best practice for package developers (and code in base
R) for coding new lines in strings?
I am developing a package to improve the debugging of Rcpp (C++) and SEXP based
C code in gdb
by providing convenience print, subset and other functions:
https://github.com/aryoda/R_CppDebugHelper
I also want to solve the Windows-only problem that you can break into the
debugger from R
only via
09-29 at 08:33 -0400, Duncan Murdoch wrote:
> On 29/09/2019 7:55 a.m., nos...@altfeld-im.de wrote:
> > Hi,
> >
> > I have a failing unit test in my package tryCatchLog on the CRAN build
> > infrastructure
> > (https://cran.r-project.org/web/checks/check_resul
Hi,
I have a failing unit test in my package tryCatchLog on the CRAN build
infrastructure
(https://cran.r-project.org/web/checks/check_results_tryCatchLog.html)
with "R Under development (unstable) (2019-09-27 r77229)"
and the unit tests just ensures consistent behaviour of R (not of my package)
Which R version are you using to produce the problem?
A few first indications:
- The regex in ".install_extras" does not match your file endings: Change
"Rmd_tmp$" into "Rmd_t$"
- Try "output: rmarkdown::html_vignette" instead of "output: html_document"
in the header of the file "ABVignetteWi
Martin, thanks for the good news and sorry for wasting your (and others
time) by not doing my homework and query bugzilla first (lesson learned!
).
I have tested the new implementation from R-devel and observe a semantic
difference when playing with the parameters:
# Test script 1
g <- "globa
Dear R friends,
to allow post-mortem debugging In my Rscript based batch jobs I use
tryCatch( ,
error = function(e)
{
dump.frames(to.file = TRUE)
})
to write the called frames into a dump file.
This is similar to the method recommended in the "Writi
t; > > unwanted spam) please let me know since I am new here.
> >
> > > Thank you very much :-)
> >
> > > J. Altfeld
> >
> > Dear J.,
> > (yes, a bit less anonymity would be very welcomed here!),
> >
> >
rivacy and defend
unwanted spam) please let me know since I am new here.
Thank you very much :-)
J. Altfeld
On Tue, 2016-02-16 at 18:25 +0100, nos...@altfeld-im.de wrote:
>
>
> If I execute the code from the "?write.table" examples section
>
> x <- data.frame(a = I
If I execute the code from the "?write.table" examples section
x <- data.frame(a = I("a \" quote"), b = pi)
# (ommited code)
write.csv(x, file = "foo.csv", fileEncoding = "UTF-16LE")
the resulting CSV file has a size of 6 bytes which is too short
(truncated):
""",3
The problem seems
14 matches
Mail list logo
