similar to: tar R command

I'm trying to understand why as.Date() is converting a the modified date of a file from August 22 to August 23. > foo <- file.info(file.to.process) > str(foo) 'data.frame': 1 obs. of 10 variables: $ size : num 5.37e+09 $ isdir : logi FALSE $ mode :Class 'octmode' int 436 $ mtime : POSIXct, format: "2010-08-22 23:14:52" $ ctime : POSIXct, format:

Hi, Recently I noticed file.copy() would discard the file mode information. Is this the expected behaviour or a bug for file.copy()? > file.create('testfile') [1] TRUE > file.info('testfile') size isdir mode mtime ctime testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39 atime uid gid uname grname

Hi, Recently I noticed file.copy() would discard the file mode information. Is this the expected behaviour or a bug for file.copy()? > file.create('testfile') [1] TRUE > file.info('testfile') size isdir mode mtime ctime testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39 atime uid gid uname grname

I've got a file that's approximately 2.2GB and it seems to be foiling file.info(). When I run `stat' from the shell I get zooey:> stat data.csv File: `data.csv' Size: 2271197563 Blocks: 4440280 IO Block: 4096 regular file Device: 342h/834d Inode: 9994308 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 500/ rpeng) Gid: ( 500/ rpeng) Access:

Hi, I'm trying to remove/delete a directory usingR. I've tried the following with no success: % Rterm --vanilla > getwd() [1] "C:/Documents and Settings/hb/braju.com.R/aroma.affymetrix/test" > dir.create("foo") > file.info("foo") size isdir mode mtime ctime atime foo 0 TRUE 777 2007-02-28 14:52:10

Hi, I have a writable and readable file on a small network file system (Cisco NSLU2 Unslung; non-NTFS) that I access via a mounted drive on Windows Vista. My problem could be due to a "funny" file system/server, but here it goes: > pathname <- "Q:/foo.txt" > cat(file=pathname, "Hello world!\n") > readLines(pathname) [1] "Hello world!" >

I was trying to remove a directory and couldn't figure out why it was failing: > dir("~/p4/r-packages/IREval/Users", recursive=T) [1] "u0048513/p4/r-packages/IREval/DESCRIPTION" [2] "u0048513/p4/r-packages/IREval/R/IREval.R" [3] "u0048513/p4/r-packages/IREval/Read-and-delete-me" [4] "u0048513/p4/r-packages/IREval/tests/general.R" >

Are there any tricks associated with file.info? I just tried it on a directory folder and it returned NA for all fields for all files. I tried it on a different folder with different files and it still returned NA. I tried it on a specific file and it returned all the proper info correctly. Just wondering if there are any tricks I've overlooked.

Note that there are at least 5 separate png() devices, so Linux was not using the (default) device used on Windows. In general, the device-limits info is not on the help page because we do not know it. On Windows the default device limits depend on the OS version, 32/64-bit, RAM and the graphics hardware. This sounds like the last: you were asking for 49 megapixels which is far larger than

Hi, on Windows 7 (tested on NTFS file system) and R-devel: 1. file.info("C:/") gives NAs whilst file.exists("C:/") gives TRUE. Instead you have to do file.info("C:/."). 2. Any number of dots will do, e.g. identical(file.info("C:/........."), file.info("C:/.")) == TRUE DETAILS: # C:/ => DISCREPANCY file.exists() and file.info() >

Good day, Could the documentation of graphics devices give some explanation of how big the bitmap limits are? For example, > png("Figure1A.png", h = 7, w = 7, res = 1000, units = "cm") Results in Error: unable to start png() device, but the help page of devices doesn't explain that there are any limits or how they are determined. The wording of the error message could

hi, the text file that prompts the segfault is 4gb but only 80,937 lines > file.info( "S:/temp/crash.txt") size isdir mode mtime ctime atime exe S:/temp/crash.txt 4078192743 FALSE 666 2017-07-15 17:24:35 2017-07-15 17:19:47 2017-07-15 17:19:47 no On Sun, Jul 16, 2017 at 6:34 AM, Duncan Murdoch <murdoch.duncan at

Hi, I was playing around with inotifywait (great tool!) to see the new staged installation of source packages in action. In one terminal I'm monitoring the create/delete/move events of the installation library with: ? inotifywait -m --timefmt '%F %T' --format '%T -- %w %e %f' -e create -e delete -e move path/to/R/library/ While in another terminal I install CRAN package

On 4/25/19 04:57, Tomas Kalibera wrote: > On 4/25/19 3:11 AM, Pages, Herve wrote: >> Hi, >> >> I was playing around with inotifywait (great tool!) to see the new >> staged installation of source packages in action. In one terminal I'm >> monitoring the create/delete/move events of the installation library >> with: >> >> ? ? inotifywait -m

I have a source file with oxygen-style comments (and description & licence files), and I?m trying to build a package. oxygen & devtools seem to work, and the tarball exists, but install.packages balks. Does anyone know what?s happening? Regards, Jorgen Harmse. > roxygenise(package.dir,clean=TRUE) Setting `RoxygenNote` to "7.3.1" ? roxygen2 requires "Encoding:

For windows, how can I list only the folders in some folder? I was thinking that dir() and file.info() with isdir==TRUE being something that might work. These folders or directories are numerically named with no dot extension names or other characters. Typically, these are 3132, 3334, ... Here is what I tried. The last line is where I need more work. pData="C:/Myfiles/R/Data/" setwd

Hi I have been trawling the web, FAQs, and R manuals for help on the following issue, but have failed and was wondering if anyone has a solution to the following problem: After having installed R 2.6.2 for Windows (binary), I tried to install various packages. Every time I try loading a package (any package) via the built-in menu, I run into the following error message. >

Is the following passage from help("file.info"): "Junction points and symbolic links are followed, so information is given about the file/directory to which the link points rather than about the link." correct? Could it be that Windows was not considered? help("file.symlink") mentions several Windows-related issues, but none of those are related to the following.

read.table terminates the program if the input file is empty. Is there way to let the program continue and return me a NULL instead of terminating the program? $ Rscript read_empty.R > read.table("empty_data.txt") Error in read.table("empty_data.txt") : no lines available in input Execution halted $ cat read_empty.R read.table("empty_data.txt") $ cat

On 16/07/2017 6:17 AM, Anthony Damico wrote: > thank you for taking the time to write this. i set it running last > night and it's still going -- if it doesn't finish by tomorrow, i will > try to find a site to host the problem file and add that link to the bug > report so the archive package can be avoided at least. i'm sorry for > the bother > How big is that