On Sep 26, 2015, at 5:06 PM, cstrato wrote:
> Dear Dirk,
>
> Yes, I know, however forget for one moment R.
>
> If I use tar independent of R it still should not create these hidden files.
>
> BTW, do you know where these hidden files are stored on the Mac?
>
Please consider reading my origi
Hi Christian,
This seems like a question about OSX rather than R. You will probably have
more luck asking on an apple forum. Or just google: http://bfy.tw/1zhP
Best,
Ista
On Sep 26, 2015 8:39 PM, "David Winsemius" wrote:
>
> On Sep 26, 2015, at 2:06 PM, cstrato wrote:
>
> > Dear Dirk,
> >
> > Y
On Sep 26, 2015, at 2:06 PM, cstrato wrote:
> Dear Dirk,
>
> Yes, I know, however forget for one moment R.
>
> If I use tar independent of R it still should not create these hidden files.
>
> BTW, do you know where these hidden files are stored on the Mac?
Your first posting showed which of s
Dear Dirk,
Please do not get me wrong.
Yes, I am doing it the wrong way and I am doing it since about eight
years. Nevertheless I am still allowed to be confused when something
suddenly happens which did not happen before during all these years.
Doing it correctly will solve the problem, but
On 26 September 2015 at 23:06, cstrato wrote:
| Dear Dirk,
|
| Yes, I know, however forget for one moment R.
No we can't. Your question was about to make R CMD check happy and
'quiet'. And one answer is to feed it a properly constructed file.
|
| If I use tar independent of R it still should no
Dear Dirk,
Yes, I know, however forget for one moment R.
If I use tar independent of R it still should not create these hidden
files.
BTW, do you know where these hidden files are stored on the Mac?
Best regards,
Christian
On 09/26/15 23:01, Dirk Eddelbuettel wrote:
On 26 September 2015
On 26 September 2015 at 22:41, cstrato wrote:
| Dear Simon,
|
| Thank you very much for your help, it did solve my problems!! Great!
|
| I have googled COPYFILE_DISABLE and found the following site which does
| explain the issue with tar on Mac OS X, see:
|
http://unix.stackexchange.com/questi
Dear Simon,
Thank you very much for your help, it did solve my problems!! Great!
I have googled COPYFILE_DISABLE and found the following site which does
explain the issue with tar on Mac OS X, see:
http://unix.stackexchange.com/questions/9665/create-tar-archive-of-a-directory-except-for-hidden
Christian,
those are resource forks from your files - possibly maintained by your (likey
very old?) editor.
First, is seems that you are not creating the tar ball correctly - the correct
way is to use R CMD build which should not include resource forks nor files on
the ignore list.
That said,
Dear all,
When running R CMD check on my Mac (Yosemite 10.10.5) I get suddenly
NOTEs and WARNINGs
that my tar.gz file does contain hidden files.
However, when checking the corresponding directories with 'ls -al' (or
with mc)
none of these files does exist!! (with exception .BBSoptions).
Her
Same problem here on Mac OS X 10.10.5 with R 3.2.2 and RStudio 0.99.473.
I think dev.new() tries to find a suitable device in an interactive session
with this code
dsp <- Sys.getenv("DISPLAY")
if (.Platform$OS.type == "windows")
windows
else if (.Platform$
geDevice has been failing check for 6 weeks now with --enable-strict-barrier ,
bisected to:
r69049 | murrell | 2015-08-14 00:03:12 +0100 (Fri, 14 Aug 2015) | 2 lines
first hack at adding grid display list to recorded plot o
12 matches
Mail list logo
