On 2/18/24 00:23, Jennifer Bryan wrote:
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,
Thanks for the testing,
Tomas
Jenny
On Thu, Feb
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 2/14/24 23:43, Jennifer
On 2/14/24 23:43, Jennifer Bryan wrote:
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)"
On 2/15/24 14:09, Ivan Krylov via R-devel wrote:
В Wed, 14 Feb 2024 14:43:12 -0800
Jennifer Bryan пишет:
But in r-devel on macOS, this is silent no-op, i.e. "hello, world"
does not print:
R.version.string
[1] "R Under development (unstable) (2024-02-13 r85895)"
con <- pipe("cat")
В Wed, 14 Feb 2024 14:43:12 -0800
Jennifer Bryan пишет:
> But in r-devel on macOS, this is silent no-op, i.e. "hello, world"
> does not print:
>
> > R.version.string
> [1] "R Under development (unstable) (2024-02-13 r85895)"
> > con <- pipe("cat")
> > writeLines("hello, world", con)
I can
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,
