search for: marttila

...omething similar to 'file()'; that is, add a 'blocking' argument to unz. It's hard to say whether they would choose 'blocking = FALSE' for back compatibility or 'blocking = TRUE' for consistency with 'file()'. Regards, Iris On Fri, Oct 25, 2024, 04:47 Marttila Mikko <mikko.marttila at orionpharma.com> wrote: > Thanks Iris, Bert, and Tim. > > > > Whether unz() is blocking or not by default doesn?t seem to be documented. > Indeed, thank you Iris for finding out that explicitly opening it as > blocking would work. That made me wo...

...is the default, so remove if desired > open(conn, "rb", blocking = TRUE) > readLines(conn) > }) > ``` > > A blocking connection might be undesirable for you, in which case > someone else might have a better solution. > > On Thu, Oct 24, 2024 at 10:58?AM Marttila Mikko via R-help > <r-help at r-project.org> wrote: > > > > Dear list, > > > > I'm seeing a strange interaction with readLines() and unz() when reading > > a file without an empty final line. The final line gets dropped silently: > > > > > c...

Dear list, I'm seeing a strange interaction with readLines() and unz() when reading a file without an empty final line. The final line gets dropped silently: > cat("hello", file = "hello.txt") > zip("hello.zip", "hello.txt") adding: hello.txt (stored 0%) > readLines(unz("hello.zip", "hello.txt")) character(0) The

...>> open(conn, "rb", blocking = TRUE) >> readLines(conn) >> }) >> ``` >> >> A blocking connection might be undesirable for you, in which case >> someone else might have a better solution. >> >> On Thu, Oct 24, 2024 at 10:58?AM Marttila Mikko via R-help >> <r-help at r-project.org> wrote: >>> >>> Dear list, >>> >>> I'm seeing a strange interaction with readLines() and unz() when reading >>> a file without an empty final line. The final line gets dropped silently: >&gt...