Performed steps according to Marc's suggestions :
But not help page is not openning in Browser.
On Tue, Jul 11, 2017 at 7:28 AM, Marc Schwartz wrote:
>
>> On Jul 10, 2017, at 5:19 PM, Duncan Murdoch wrote:
>>
>> On 10/07/2017 5:02 PM, Christofer Bogaso wrote:
>>> Hi,
>>>
>>> I wanted R to open
> On Jul 10, 2017, at 5:19 PM, Duncan Murdoch wrote:
>
> On 10/07/2017 5:02 PM, Christofer Bogaso wrote:
>> Hi,
>>
>> I wanted R to open any Help page in html permanently.
>>
>> So 1st I created .Rprofile file with below code in terminal:
>>
>> touch ~/.Rprofile
>>
>> open -a Textedit ~/.Rpr
On 10/07/2017 5:02 PM, Christofer Bogaso wrote:
Hi,
I wanted R to open any Help page in html permanently.
So 1st I created .Rprofile file with below code in terminal:
touch ~/.Rprofile
open -a Textedit ~/.Rprofile
And then in the .Rprofile file, I wrote below code :
options(help_type = ‘ht
Thanks Don,
Can you perhaps make that a little closer to being reproducible for people who
might want to try it on newer hardware? (packages, location of input file).
(And by the way, xterm? What did Terminal.app do to you?)
This, along with a thread from 2014 that Google dug up, strongly sugge
Hi,
I wanted R to open any Help page in html permanently.
So 1st I created .Rprofile file with below code in terminal:
touch ~/.Rprofile
open -a Textedit ~/.Rprofile
And then in the .Rprofile file, I wrote below code :
options(help_type = ‘html’)
However after that when I start R (from Term
For what it's worth, here is my experience on a late 2013 Mac Pro.
(I normally run R from an xterm shell within an X Windows context)
The best performance for displaying the image on-screen uses cairographics and
Polypath. It's the only one fast enough to be satisfactory for interactive use,
in
Hi Peter, outputting to PDF made a huge difference! It ran for only 15 seconds
and there was no trailing unresponsive prompt. The PDF ended up being around
2Mb and opened and displayed almost immediately in Preview.
I did watch the system when I was outputting to the quartz device last time and
Pretty clear that the process is getting stuck in Apple-graphics land, then.
This could be inefficiency of the device driver, but also just ... Apple. Could
you try running the same thing to a PDF (AFAIR, just open the device with
pdf(file="myplot.pdf"), then print(plt), then dev.off()). It woul