Command-line editing re-visited.
A couple of small points.
On Fri, 7 Sep 2001, Rolf Turner wrote:
...
(b) Thomas Vogels suggested
Once you fire up the newly built R, you can verify that the readline
library was picked up correctly using the capabilities function:
R> capabilities("cledit")
cledit
TRUE
When I did
> capabilities("cledit")
I got logical(0) The help on capabilities evinced no reference to ``cledit''. Is something missing here?
You need 1.3.1 for this.
So, I now come to my QUESTION: How ***do*** you persuade the R command-line editor to use vi syntax? Ideally I would like to be able to put something into an ``init'' file (.Renviron???) so that I always get vi syntax when I fire up R. Failing that, something that I can put into a .First() function.
Try man readline: You want something like `set keymap vi-insert' in your .inputrc, I think.
Brian D. Ripley, ripley at stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272860 (secr) Oxford OX1 3TG, UK Fax: +44 1865 272595 -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-help-request at stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._