similar to: file mode lost in file.copy()?

Hello, The documentation for the tar command leads me to think there is an internal implementation when the command can't be found in the OS. However, it doesn't seem to be the case, as I get an empty .tar file generated on a small example I made : > dir(pattern = "jpg") [1] "MA56237502_635.jpg" > file.info("MA56237502_635.jpg")

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:

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:

I'm using RedHat 7.2 with kernel 2.4.18-26.7.xsmp and root mount using ext3. And I have simple test.pl script: #!/usr/local/bin/perl open FILE, ">testfile"; while(1){ print FILE "Test.\n" or die $!; } It's died when the file size is 2147483647 and give error message: "File size limit exceeded" and I run "cat testfile testfile >>

Hi all I wish to create a ps file of a picture produced in R. With my limited R, I see two ways: 1. Print direct to the postscript device 2. Print to the screen, and save to ps using dev.print. I want a white (not transparent) background. Option 1 above works fine, but 2 does not: even when I say I want a white background, I get transparent; perhaps I misread the help files. Here's some R

While checking packages against R 2.13.0-beta on Windows, I have run into a few strange error messages related to copying files. The errors all relate to file.copy() and have the form of: Error in Sys.chmod(to[okay], file.info(from[okay])$mode, TRUE) : 'mode' must be of length at least one After half a day of tinkering, the best reproducible example I can come up with involves using

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

I am testing a Btrfs root file system with Debian (kernel 2.6.32) under KVM. jason@vrtl:~$ touch testfile jason@vrtl:~$ cp --reflink testfile /tmp cp: failed to clone `/tmp/testfile'': Invalid argument This is with GNU Coreutils 8.0 taken from debian Sid. Is this a Coreutils issue, a Btrfs problem or something in my local configuration? All the other issues that I have encountered so

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:

Dear r-helpers, I am looking for an R-equivalent for the eval-function in javascript which can interpret a string as code on runtime, thereby allowing things like for (i in c(1:2)) { eval(items + "i") <- read.csv(eval(filename+ i), dec=","); } which would execute (with filename="testfile"): items1 <- read.csv(testfile1, dec=","); items2 <-

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!" >

Hi, I have a function knit_expand() and its source/Rd are below: https://github.com/yihui/knitr/blob/master/R/template.R#L43-L44 https://github.com/yihui/knitr/blob/master/man/knit_expand.Rd When I run R CMD check on the package I get this warning (with both R 2.15.2 and R-devel): * checking for code/documentation mismatches ... WARNING Codoc mismatches from documentation object

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() >

Hi, Suppose I have x = parse(text = " {y=50+50+50#'asfasf' } ") now x is an expression with some src attributes. > x expression({y=50+50+50#'asfasf' }) attr(,"srcfile") <text> attr(,"wholeSrcref") {y=50+50+50#'asfasf' } My question is, how can I get my string back (the string passed to parse() as the text argument)? >

Hi, The problem arises when I lazyLoad() the .Random.seed from a previously saved database. To simplify the process of reproducing the problem, see the example below: ## this assignment may not really make sense, but illustrates the problem delayedAssign('.Random.seed', 1L) typeof(.Random.seed) # [1] "integer" rnorm(1) # Error in rnorm(1) : # .Random.seed is not an integer

Hi, The problem arises when I lazyLoad() the .Random.seed from a previously saved database. To simplify the process of reproducing the problem, see the example below: ## this assignment may not really make sense, but illustrates the problem delayedAssign('.Random.seed', 1L) typeof(.Random.seed) # [1] "integer" rnorm(1) # Error in rnorm(1) : # .Random.seed is not an integer

Hi, A Windows user asked me a question and I believe this is a bug of R 3.0.0 under Windows: > plot(1:10) > savePlot('test.wmf') Error in .External(C_savePlot, device, filename, type, restoreConsole) : Incorrect number of arguments (4), expecting 3 for 'savePlot' > sessionInfo() R version 3.0.0 (2013-04-03) Platform: x86_64-w64-mingw32/x64 (64-bit) locale: [1]

Hi all, Since roxygen is a great help to document R packages, I am wondering if there exists an approach to go back from the raw Rd files to roxygen-documentation? E.g. turn "\author{Somebody}" into "@author Somebody". This sounds ridiculous, but I believe it helps in the long term for me to maintain R packages. Thanks! Regards, Yihui -- Yihui Xie <xieyihui at

Hi, I observed a slight problem in deparse(): it will add spaces around most operators except /. I wonder if this is easy to fix. I know this is quite trivial, but I will appreciate if / is not treated as an exception. Examples: > deparse(expression(1/1)) [1] "expression(1/1)" > deparse(expression(1+1)) [1] "expression(1 + 1)" > deparse(expression(1%in%1)) [1]

Hi, I'm aware of the definition of a "valid filename" in .SweaveValidFilenameRegexp, but I think it might be better to quote the filename when it contains spaces instead of just giving a warning. This should bring us safer LaTeX code (although I never use spaces in paths). Here is the simple patch: Index: src/library/utils/R/SweaveDrivers.R