similar to: readLines() and unz() and non-empty final line

Displaying 20 results from an estimated 10000 matches similar to: "readLines() and unz() and non-empty final line"

2024 Oct 25
1
readLines() and unz() and non-empty final line
Hi again, The unz connection is non-blocking by default. I checked do_unz which calls R_newunz which calls init_con and the only place in any of those functions that sets 'blocking' is init_con which sets it to FALSE: https://github.com/wch/r-source/blob/0c26529e807a9b1dd65f7324958c17bf72e1de1a/src/main/connections.c#L713 I'll open an issue on R-bugzilla and see if they're
2024 Oct 24
3
readLines() and unz() and non-empty final line
But note: > zip("hello.zip", "hello.txt") updating: hello.txt (stored 0%) > readChar(unz("hello.zip","hello.txt"),100) [1] "hello" I leave it to you and other wiser heads to figure out. Cheers, Bert On Thu, Oct 24, 2024 at 8:57?AM Iris Simmons <ikwsimmo at gmail.com> wrote: > Hi Mikko, > > > I tried running a few
2024 Oct 25
1
readLines() and unz() and non-empty final line
Hi, you could use "scan" instead, it seems to work fine also when wrapped around "unz". Or, alternatively, you could use "unzip" instead of "unz". It works as expected, i.e. reads the last incomplete line and throws a warning about this. So it seems to me that "unz" creates a non-blocking connection, whereas "unzip" creates a
2007 Dec 19
1
unexpected behavior from gzfile and unz
I get unexpected behavior from "readLines()" and "scan()" depending on how the file is opened with "gzfile" or "unz". More specifically: > file <- gzfile("file.gz") > readLines(file,1) [1] "a\tb\tc" > readLines(file,1) [1] "a\tb\tc" > close(file) It seems that the stream is rewound between calls to readLines.
2003 Jul 11
2
unz()
I am having problems getting the unz() function to work as a connection to start reading a file... z <- unz("c:/temp/stoxx.zip", "close_tmi_components.txt", "r") readLines(z,2) yields the following problems: > z <- unz("c:/temp/stoxx.zip", "close_tmi_components.txt", "r") Error in unz("c:/temp/stoxx.zip",
2009 Jul 28
2
Looking for example of usage of function unz
I would greatly appreciate some example of correct usage of function unz. I have to download and uncompress the following web compressef file: ftp://ftp.sanger.ac.uk/pub/mirbase/targets/v5/arch.v5.txt.homo_sapiens.zip I tried the following command that does not work: Targets.rec <- readLines(zz <- unz("ftp://ftp.sanger.ac.uk/pub/mirbase/targets/v5/arch.v5.txt.homo_sapiens.zip"))
2003 Jul 24
0
unz( "x.zip", "y.csv" ) != pipe( "unzip -p x.zip y.csv" )
Not sure this is a bug in R. Maybe its a bug in my understanding of unz(). The character 'b2' (hexadecimal) is in position 535 of line 1 of 'naughty.csv'. This character appears as superscript '2' and came to me in an EXCEL file that I converted to text in a comma separated ( *.csv ) format. The first line gets truncated by readLines after 534 characters using unz():
2005 Aug 24
1
How to get the list of the files when you read zip file by gzfile or unz
Dear List, Does somebody know how to get the filename lists in the ziped when "gzfile" or "unz" command is used ? Thanks for your help. Shawn Lee -- The information contained in this communication and any atta...{{dropped}}
2025 May 23
1
Formatting zeroes with prettyNum
Tim, The purpose of the `replace.zero` argument is to allow longer replacements. See for example the behaviour with a character vector input: > prettyNum("0", zero.print = "- ", replace.zero = TRUE) [1] "- " I'm pretty sure this is a bug, and have now posted the relevant details on r-devel. A fix would be below. Best, Mikko diff --git
2025 May 23
1
Formatting zeroes with prettyNum
You fed it two characters, "dash" and "space" and it only wanted one character so it truncated to the first character and warned you that that's what it did. If you had your space before the dash, it would have used that as your replacement character > prettyNum(0, zero.print = " - ", replace = TRUE) [1] " " Warning message: In .format.zeros(x,
2012 May 30
1
reading file in zip archive
Hi List I have a series of zip archives each containing several files. One of these files is called goCats.txt and I would like to read it into R from the archive. It's a simple tab delimited text file. pathToZip <- '/home/iain/Documents/Work/Results/bovineMacRNAData/deAnalysis/afInfection/commonNorm/twoHrs/af2hrs.zip' z <- unz(pathToZip, 'goCats.txt', 'r') zT
2025 May 27
1
Bug in prettyNum
Thanks for the contribution Mikko! For testing future patches, you can actually do it right in the web browser, thanks to Heather Turner's R Dev Container, see instructions here https://contributor.r-project.org/r-dev-env/container_setup/ Best Toby On Mon, May 26, 2025 at 6:28?PM Martin Maechler <maechler at stat.math.ethz.ch> wrote: > Thank you, Marttila and Ivan, > > As
2025 May 26
1
Bug in prettyNum
Thank you, Marttila and Ivan, As the original author of prettyNum() {etc ..}, I will commit such a bug fix to R-devel (and probably port it to R 4.5.0 patched) quite soon (but not yet today). Best regards, Martin Maechler >>>>> Ivan Krylov via R-devel >>>>> on Fri, 23 May 2025 17:14:57 +0300 writes: > ? Fri, 23 May 2025 11:47:33 +0000 >
2012 Jan 31
2
how to unzip files in R
Hi, I have downloaded a bunch of bz2 files. I wonder if R will be able to unzip them in a batch mode or even one at a time? I was looking at the unz function. But it didn't work well. Say I have a bz2 file in H:/Temp/65502805_532.pair.bz2. Anyone has any suggestion? thanks John > setwd("H:\\Temp\\") > getwd() [1] "H:/Temp" >
2010 Sep 20
0
unz() ignores encoding argument
Hi! I'm trying to read individual files from a ZIP archive, using the unz() function. Some of the files contain non-ASCII characters and I'd like to avoid unpacking them in a temporary directory. My problem is that unz() seems to ignore the encoding="latin1" option I need to read the non-ASCII characters properly. I can't find a clear indication in the documentation that
2025 May 23
1
Bug in prettyNum
? Fri, 23 May 2025 11:47:33 +0000 Marttila Mikko via R-devel <r-devel at r-project.org> ?????: > When called with a numeric vector, the `replace.zero` argument is > disregarded. > > > prettyNum(0, zero.print = "- ", replace.zero = TRUE) > [1] "-" > Warning message: > In .format.zeros(x, zero.print, replace = replace.zero) : >
2025 May 23
1
Formatting zeroes with prettyNum
Dear list, Have I stumbled upon a bug, or am I holding `prettyNum()` wrong? Please see below. Best, Mikko > prettyNum(0, zero.print = "- ", replace.zero = TRUE) [1] "-" Warning message: In .format.zeros(x, zero.print, replace = replace.zero) : 'zero.print' is truncated to fit into formatted zeros; consider 'replace=TRUE' > prettyNum(0, zero.print =
2016 Feb 25
2
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
On 23.02.2016 14:06, Mikko Korpela wrote: > On 23.02.2016 11:37, Martin Maechler wrote: >>>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: >> >> > Dear R developers >> > I think I have found a bug that can be reproduced with two lines of code >>
2006 Jun 30
2
incomplete final line found by readLines on ...
Dear R-users I need to read some text files produced by some other software. I used readLines (with n = -1 ) command and then tried to find some numbers I liked to extract or some line numbers I like to know. The problem is that there is no empty line at the end of the text files. R gave me this warning below; In addition: Warning message: incomplete final line found by readLines on
2016 Feb 29
1
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
I have just committed your first patch (the strlen() replacement) to R-devel, and will soon put it in R-patched as well. I wont have time to look at this again before the 3.2.4 release, so your file.show() patch isn't going to make it unless someone else gets to it. There's still a faint chance that I'll do more in R-devel before 3.3.0, but I think it's best if there were bug