On 8 September 2010 at 13:01, Jeffrey Horner wrote: | This is great news! I don't know how I could survive without bash's vi | style editing and command completion... | | Here's my PATH variable which sets the Rtools paths first, then MinGW: | | horn...@hornerj-win ~ | $ echo $PATH | /c/Rtools/bin:/c/Rtools/perl/bin:/c/Rtools/MinGW/bin:/c/localbin:/mingw/bin:/bin:/usr/bin:/usr/lo | cal/bin:/c/Program Files (x86)/R/R-2.11.1/bin:/c/Program Files | (x86)/CollabNet/Subversion Client: | /c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1. | 0/:/c/Program Files (x86)/MiKTeX 2.8/miktex/bin | | I'm going to follow the "R Installation ..." manual to compile R on | Windows and learn a bit about the build process. From there, I intend | to "port" some open source libraries that have support for being | compiled with MS VC++ over to MinGW. | | Aside from my PATH variable, are there other things about my | development environment I should be aware of?
FWIW I always add rxvt (taken from Cygwin's repos) so that I can launch an 'xterm' alike from the usual shortcut by having this as the command in Cygwin.bat: rxvt -sr -sl 2500 -sb -geometry 90x30 -fg wheat -bg gray10 -tn rxvt \ -fn 'Lucida Console-14' -e /usr/bin/bash --login -i The last time I set that up I left myself a note that I got hints from http://blasphemousbits.wordpress.com/2007/02/12/rxvt-solves-many-cygwin-woes/ and also see http://www.saltycrane.com/blog/tag/cygwin/ Those links may by now be stale. Hth, Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel