I've now tested with:
> R.version.string
[1] "R Under development (unstable) (2024-02-16 r85931)"
and all of the previously mentioned examples now work as expected on macOS.
Thanks for the quick fix,
Jenny
On Thu, Feb 15, 2024 at 8:02 AM Tomas Kalibera
wrote:
>
> On
Hello,
I've noticed a specific type of pipe() usage that works in released R, but
not in r-devel.
In 4.3.2 on macOS, I can write to a connection returned by pipe(), i.e.
"hello, world" prints here:
> R.version.string
[1] "R version 4.3.2 (2023-10-31)"
> con <- pipe("cat")
> writeLines("hello, wo
Hi,
I am writing a test that consults the serialization version of an `.rds`
file.
An attractive way to get this is:
tools:::get_serialization_version() # reports just version
which calls
.Internal(serializeInfoFromConn() # reports much more
but neither is truly exported for public use.
Is t
Hello,
I'm seeing a nuisance warning when I run `R CMD check --as-cran
whatever_x.y.z.tar.gz`.
I generally work with these options set:
options(
warnPartialMatchArgs = TRUE,
warnPartialMatchAttr = TRUE,
warnPartialMatchDollar = TRUE
)
And I see this:
* checking use of SHLIB_OPENMP_*FLAGS
Hello,
I'm interested in moving text from and to the clipboard that cannot
necessarily be represented in the native encoding. So, really, this is
about Windows.
I can successfully read from the clipboard by specifying the format that
corresponds to unicode text.
>From R >=2.7.0, it seems you sho
Hello,
I'm interested in moving text from and to the clipboard that cannot
necessarily be represented in the native encoding. So, really, this is
about Windows.
I can successfully read from the clipboard by specifying the format that
corresponds to unicode text.
>From R >=2.7.0, it seems you sho