---

Some useful links for the R statistical software package

---

R/CRAN
An introduction to R
R quick 'reference card'
R Project
R News
R Mailing Lists
Junjia Zhu's guide to using the command line to control R variables.
Baojun Qiu's compilation of useful R tips for Stat 515 students.
Roger Peng's guide to calling C from R.

---

Editing: It is vital that you use a good editor for typing your R programs --- the editor will indent the code, highlight/color keywords (e.g. function names), match parentheses, thereby helping you find your errors more easily and making your code much more readable. Debugging your programs will be a nightmare otherwise.

---

For Unix/Linux: I believe emacs is the most flexible editor. It has the added advantage of also `understanding' latex, C, C++, python, and lots of other programming languages.

If you end up using emacs, you may want to try ESS (emacs speaks statistics), which is a great environment for you to run and debug your R programs. For help on this go to ESS OR ESS (emacs speaks statistics) within the R project website

---

For Windows: Notepad++ is apparently relatively easy to use and very convenient. Winedt is an option, though perhaps much less sophisticated than Notepad++ Also try: R for Windows Frequently Asked Questions

For emacs/ESS, on Windows, try: John Fox's guide may be a good starting point.

---

---

For Mac OSX: Simply download and use Aquamacs from here . There is no effort involved in having emacs 'understand' your R and Latex code. Just call your function `myfunctionname.R' for R or `myfunctionname.tex' for latex and emacs will know that you are typing R code or latex code. Some people use the in-built editor in R, but I think this is inferior to using emacs/aquamacs or some other specialized editor.

---

---