I am not a Mac user, but I do use Linux and I would recommend not running R
with sudo unless you are an admin ninja. That defensive practice would render
the answer to your question moot.
It is possible that your problem may have started with inappropriate use of
sudo in configuring java, but
If your goal is to interoperate with Python (esp. when using numpy and friends)
then Anaconda is actually a good option... just learn how activate a conda
environment before doing anything within that ecosystem and remember that each
conda environment you create will be independent of all
Are you really entering an asterisk as part of the file name? That sounds like
an extremely bad idea.
On October 23, 2019 3:13:48 PM PDT, Bryan Hanson wrote:
>Duncan…
>
>I’m creating a new file. The menu item is “New Document”. I called it
>*.R to distinguish it from “New Rd Document”, and
I am glad my response helped direct you toward a resolution, but antivirus
interference did not actually occur to me. Thanks for reporting back.
On January 1, 2020 7:23:12 AM PST, Spencer Graves
wrote:
> Thanks to Jeff Newmiller for his reply. He was correct. My
>Bitdefender in
"Permission denied" suggests that this is not related to R. Perhaps you ran R
with elevated permissions yesterday?
On December 25, 2019 8:37:36 AM PST, Spencer Graves
wrote:
>Hello, All:
>
>
> I just upgraded to R 3.6.2 and suddenly got, "cannot open
>compressed file" with "R CMD build"
Use a cloud solution?
On March 28, 2020 9:44:45 AM PDT, Prathiba Natesan
wrote:
>Hi all:
>I am looking for a high end performance desktop/laptop for statistical
>simulations. I typically run hundreds of thousands of simulations using
>JAGS and other packages. Any suggestions?
>Cheers
>P
>
>
; under R 3.6.X and my old 10.11 OSX, but now I know
>
>how to get it done.
>
>
>
>On 6/6/20 4:29 PM, Jeff Newmiller wrote:
>> AFAIK tgz is one possible file name extension equivalent to .tar.gz,
>which implies gzip compression, so I think Bob was just being a bit
>slop
AFAIK tgz is one possible file name extension equivalent to .tar.gz, which
implies gzip compression, so I think Bob was just being a bit sloppy when he
wrote tar.tgz.
Key point is not that a particular compression makes a difference, but that the
check needs to be run on a source archive
Also, symlinking an X.Y R version package library to any other major-minor
version is never supported (even if it sometimes works). Re-install your
packages when the minor version Y increments.
On June 8, 2021 5:07:28 PM PDT, Simon Urbanek
wrote:
>
>You seem to have entirely non-standard
There are many of these. Some of these "solutions" copy the actual installed
packages and then run "update.packages"... which is a very bad idea. Other
solutions identify the names of the packages and install fresh (good idea) but
they will hiccup when you install from non-standard sources. So
Even better is to learn one of the many ways to start R in a working directory
of your choice, so you don't have to mix code and data from different projects
together in one directory just because that happens to be where your default R
icon sets it up.
Some ways:
a) Use Terminal and the cd
I cannot address your observed symptoms, but shouldn't you have already
upgraded your R to the latest version before asking this?
On September 29, 2021 11:17:02 AM PDT, Jeffrey Rosenthal
wrote:
>Hello. I often use R from the command-line (i.e. just typing "R")
>within the "Terminal"
Generating patch files is one of the most fundamental capabilities of git.
Changes to the Linux kernel are (almost?) universally submitted via patch files
generated from git.
Re git and empty directories... git is structurally incapable of recording them
in the repo. A common workaround is to
Operating systems are designed to be as backward-compatible as possible... R
Core doesn't generally know what distinguishing features will identify a new OS
until it is released, nor what it will be called, so R has a handicap.
On February 11, 2023 1:12:42 PM PST, Christofer Bogaso
wrote:
14 matches
Mail list logo
