Hi,
after a period of testing this kind of daemon (perl/ruby) I must say it's hard to catch all eventualities. I solved the problems of synchronisation between TM and R, even if R does not output something, I caught the statement readline(), and and ... but still there are lot of problems. The biggest one is to catch ANY error while typing. I could solve it for normal typos, but, for instance, if I write "qu it" the daemon halted immediately and this could be very crucial (And I have no idea to fix it). An other problem is the statement "source()". That would mean that the source code must also piped through this daemon. Not mentioning R's statement completion if I type "4+" press enter, ... the daemon will give an error, and and and. Now I have a version which works very fast but only with a lot of exceptions.
So, by my opinion, it will cost too much effort to write such a daemon, and finally it ends up with something that R.app does. So why to invent the wheel twice?
Then I went back to communicate with R via AppleScript. I tried out whether a R terminal running in a shell (iTerm) would be fast than R.app, but it seems to me that is not the case.
So my summary is to improve the commands within the default R-bundle is up to now the best choice, but this will be an other thread.
Bye
-Hans