On 20.12.2007, at 19:43, Charilaos Skiadas wrote:
On Dec 20, 2007, at 1:04 PM, Hans-Jörg Bibiko wrote:
On 20.12.2007, at 17:28, Charilaos Skiadas wrote:
I just started using this and it look pretty sweet so far (though admittedly I haven't gone far ;) ). The only problem I am seeing so far is with plots, the first time they are generated. If the plot window is closed, and I run something like "plot (1:10)", sometimes I get:
326:331: execution error: System Events got an error: NSReceiverEvaluationScriptError: 4 (1) or sometimes 331:336: execution error: System Events got an error: NSReceiverEvaluationScriptError: 4 (1)
Did you open a quartz device or x11? The error message tends to be sent from quartz. Did you installed CarbonEL package? Anyway I will try to reproduce it.
No I did not open a quartz device by myself, so far I got this error from three different places:
- 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?
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.
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