[TxMt] R daemon running 'inside' of TM + QUESTION on ram drive

[Charilaos Skiadas]

On Dec 20, 2007, at 2:11 PM, Hans-Jörg Bibiko wrote:

> On 20.12.2007, at 19:43, Charilaos Skiadas wrote:
>> On Dec 20, 2007, at 1:04 PM, Hans-Jörg Bibiko wrote:
>>
>> No I did not open a quartz device by myself, so far I got this  
>> error from three different places:
>> 1. When for the first time a quartz window opened as a consequence  
>> of a call to "plot", and a couple more times later
>> 2. When A window opened by a call to a lattice command, namely  
>> histrogram. Strangely enough, once that happened once, from that  
>> point on neither plot or histogram gave me another error
>> 3. Whenever I try to open a help page, unless that item is already  
>> open in help (help pages open within R.app for me).
> Wait. I look for 'System Events got an error:  
> NSReceiverEvaluationScriptError: 4' at the internet . All pages  
> refer to an applescript error. But the Rdaemon do not need  
> applescript, actually??
> Did you run R.app at the same time?
>

Yes of course, if my computer is on, then R.app is running  ;)
Ok, I just figured out what I was doing wrong, stupid of me. An R  
Console command was used instead because I was just pressing return.  
I was thinking this would be the trigger for the Rdaemon command. So  
it wasn't your code that was running at all, it was my old crappy  
code from the RConsole/Applescript days. Using enter instead of  
return, i.e. your code, things work just fine. Graphs open in x11  
windows. Help is still a problem though, TM just stalls.

Why not set return to be the trigger for the execute command, instead  
of enter?

killing is also still a problem.

>> I see. Then it's probably a good idea, though 80M might be too  
>> much, I dunno. Why did you set it to 80M? Perhaps the size can be  
>> customizable as well.
> I'm just working on that ;)
>
>>
>> Btw, a thing to consider adding is to make it so that, when on the  
>> last line, using up/down arrows moves you among the history items,  
>> like the R.app GUI does. This action has been built too much into  
>> my muscle memory by now.
> Hmm... I will sleep about it whether there is an easy to implement  
> this.

The last line is the only one not ending with a newline character, so  
it should be doable to detect that.
>
>> Btw, I had some problems killing the daemon. I tried kill+tab,  
>> which resulted in the message "Rdaemon is not running!". Then  
>> trying start+tab resulted in "Rdaemon is already running". Indeed  
>> the R daemon seems to work throughout this process. ps gives me:
> It's also already fixed. I changed the command line to call R, and  
> I forgot to change the grep regexp.
>
>> Btw, when the daemon first started, it started X11. Is that  
>> necessary? I usually don't have X11 running.
> I did this for safety reasons. chooseCRANmirror() or other stuff  
> opens a tk menu.
> I already set options(menu.graphics=F) while starting but sometimes  
> I see such a tk menu ? Maybe it's caused by the issue that X11 runs?
> I'll check this
>
> --Hans

Haris Skiadas
Department of Mathematics and Computer Science
Hanover College