You need to figure out where R is installed, probably in
c:\program files\R-3.4\bin
If you go to that directory (you can do it with this command in a command
window):
cd c:\progra~1\R-3.4\bin
Then start R like this:
.\R.exe --vanilla
Dan
- Original Message -
> From: "Jurat Shayidin
Dear Dan :
I tried same command in terminal, but I got an error : 'R' is not
recognized as internal or external command, operable program or batch
file. should
I change the directory under the current package working directory ? How
can I fix this error ? Any quick solution ? Thanks a lot
Best reg
Don't do this in RStudio, do it at the command line/terminal. Type in R
--vanilla. You won't get the same interface as RStudio but you can see if the
problem persists.
Dan
- Original Message -
> From: "Jurat Shayidin"
> To: "Kasper Daniel Hansen" , "bioc-devel"
>
> Sent: Friday, Nov
Dear Kasper :
Thanks for your explanation. However, I opened the shell from Rstudio and
type the command R --vanilla, seems it works fine, but still not sure about
efficiency of using R -vanilla. I am not confident about using R commands,
so is there any quick example that I can practice and unders
You're bing asked to use
R --vanilla
because you have a non-standard problem, exemplified by the fact that what
you have problems with (installing CRAN packages) works for thousands of
users of Bioconductor (certainly for me). This suggests that there is
something wrong with something on your co
On 11/11/2016 12:09 PM, Jurat Shayidin wrote:
sorry for this simple question. why use R vanilla ? not familiar enough
with this term.
It's not R vanilla, but R --vanilla; see
R --help
On Fri, Nov 11, 2016 at 5:51 PM, Martin Morgan <
martin.mor...@roswellpark.org> wrote:
On 11/11/2016 11
sorry for this simple question. why use R vanilla ? not familiar enough
with this term.
On Fri, Nov 11, 2016 at 5:51 PM, Martin Morgan <
martin.mor...@roswellpark.org> wrote:
> On 11/11/2016 11:42 AM, Jurat Shayidin wrote:
>
>> I'll keep this in mind. Thanks for reminding. Could you please elabor
On 11/11/2016 11:42 AM, Jurat Shayidin wrote:
I'll keep this in mind. Thanks for reminding. Could you please elaborate
your answer on my doubt ? Thanks
On Fri, Nov 11, 2016 at 5:27 PM, Martin Morgan <
martin.mor...@roswellpark.org> wrote:
Please respond on the mailing list, so that others in s
Thanks for reminding, I'll keep this in mind. I figured out that after
clean R session, problem is solved. But how can I avoid this sort of issue
and facilitate the building package ? How can make R session vanilla ? Any
recommendation for configuration before start building packages ? Could you
el
I'll keep this in mind. Thanks for reminding. Could you please elaborate
your answer on my doubt ? Thanks
On Fri, Nov 11, 2016 at 5:27 PM, Martin Morgan <
martin.mor...@roswellpark.org> wrote:
> Please respond on the mailing list, so that others in similar situations
> can benefit / contribute.
>
On 11/11/2016 09:44 AM, Jurat Shayidin wrote:
Dear BiocDevel:
I ran into the issue after installed devel version of R and Bioc 3.4.
Because my packages depends on some packages from CRAN repository, now I
failed to installed paclages from CRAN. I don't have problem when I used
released version o
Dear BiocDevel:
I ran into the issue after installed devel version of R and Bioc 3.4.
Because my packages depends on some packages from CRAN repository, now I
failed to installed paclages from CRAN. I don't have problem when I used
released version of R. Because new packages must coordinate with d
12 matches
Mail list logo
