Respected r-help readers, I am a bit uncomfortable because my favourite text editor vim does not speak statistics. So I obtained a perl-script made to get vim to interact with a lisp interpreter and had it set up so vim sends text to a socket and R executes - but there are some irreproducible errors and I don't understand the perl-script. Could someone show me an alternative method to start R in a way that it listens to a unix domain socket? I know about the R function socketConnection() but this creates tcp sockets which I don't know how to send text to. Good day Johannes Ranke
On Tue, 5 Aug 2003, Johannes Ranke wrote:> Respected r-help readers, > > I am a bit uncomfortable because my favourite text editor vim does not > speak statistics. So I obtained a perl-script made to get vim to > interact with a lisp interpreter and had it set up so vim sends text to > a socket and R executes - but there are some irreproducible errors and I > don't understand the perl-script. > > Could someone show me an alternative method to start R in a way that it > listens to a unix domain socket? I know about the R function > socketConnection() but this creates tcp sockets which I don't know how > to send text to.I'm not sure that this is possible. The editor that does speak statistics doesn't do it this way: it takes over stdin and stdout instead. -thomas
Maybe Matching Threads
- parallel:::newPSOCKnode(): background worker fails immediately if socket on master is not set up in time (BUG?)
- parallel:::newPSOCKnode(): background worker fails immediately if socket on master is not set up in time (BUG?)
- parallel:::newPSOCKnode(): background worker fails immediately if socket on master is not set up in time (BUG?)
- readBin on binary non-blocking connections (Windows & Unix differences/bugs)
- socket problems (maybe bugs?)