course
/
r4ds
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix typos (#418) 

* Fix typos

* Fix typos

* Fix typos
This commit is contained in:
behrman 2016-10-03 05:16:50 -07:00 committed by Hadley Wickham
parent 40450eca3c
commit 0147bd0260
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
workflow-basics.Rmd
View File

@ -103,9 +103,9 @@ Quotation marks and parentheses must always come in a pair. RStudio does its bes
+
```
The `+` tells you that R is waiting for more input; it doesn't think you're done yet. Usually that means you've forgotten either a `"` or a `)`. Either add missing pair, or press ESCAPE to abort the expression and try again.
The `+` tells you that R is waiting for more input; it doesn't think you're done yet. Usually that means you've forgotten either a `"` or a `)`. Either add the missing pair, or press ESCAPE to abort the expression and try again.
If you make an assignment, you don't get to see the value. You're then tempted to immediately double check the result:
If you make an assignment, you don't get to see the value. You're then tempted to immediately double-check the result:
```{r}
y <- seq(1, 10, length = 5)

4
workflow-projects.Rmd
View File

@ -95,8 +95,8 @@ In your favorite OS-specific way, search your computer for `diamonds.pdf` and yo
In summary, RStudio projects give you a solid workflow that will serve you well in the future:
* Create an RStudio project for each data analyis project.
* Keep data files there; we'll talk about a bit later importing in [import].
* Create an RStudio project for each data analysis project.
* Keep data files there; we'll talk about importing a bit later in [import].
* Keep scripts there; edit them, run them in bits or as a whole.
* Save your outputs there.

6
workflow-scripts.Rmd
View File

@ -6,11 +6,11 @@ So far you've been using the console to run code. That's a great place to start,
knitr::include_graphics("diagrams/rstudio-editor.png")
```
The script editor is a great place to put code you care about. Keep experimenting in the console, but once you have written code that work and does what you want, put it in the script editor. RStudio will automatically save the contents of the editor when you quit RStudio, and will automatically load it when you re-open. Nevertheless, it's a good idea to regular save your scripts regular and to back them up.
The script editor is a great place to put code you care about. Keep experimenting in the console, but once you have written code that works and does what you want, put it in the script editor. RStudio will automatically save the contents of the editor when you quit RStudio, and will automatically load it when you re-open. Nevertheless, it's a good idea to regularly save your scripts and to back them up.
## Running code
The script editor is also a great place to build up complex ggplot2 plots or long sequences of dplyr manipulations. The key to using the script editor effective is to memorise one of the most important keyboard shortcuts: Cmd/Ctrl + Enter. This executes the current R expression in the console. For example, take the code below. If your cursor is at █, pressing Cmd/Ctrl + Enter will run the complete command that generates `not_cancelled`. It will also move the cursor to the next statement (beginning with `not_cancelled %>%`). That makes it easy to run your complete script by repeatedly pressing Cmd/Ctrl + Enter.
The script editor is also a great place to build up complex ggplot2 plots or long sequences of dplyr manipulations. The key to using the script editor effectively is to memorise one of the most important keyboard shortcuts: Cmd/Ctrl + Enter. This executes the current R expression in the console. For example, take the code below. If your cursor is at █, pressing Cmd/Ctrl + Enter will run the complete command that generates `not_cancelled`. It will also move the cursor to the next statement (beginning with `not_cancelled %>%`). That makes it easy to run your complete script by repeatedly pressing Cmd/Ctrl + Enter.
```{r, eval = FALSE}
library(dplyr)
@ -55,7 +55,7 @@ knitr::include_graphics("screenshots/rstudio-diagnostic-warn.png")
1. Go to the RStudio Tips twitter account, <https://twitter.com/rstudiotips>
and find one tip that looks interesting. Practice using it!
1. What other common mistakes will RStudio diagonistcs reports? Read
1. What other common mistakes will RStudio diagnostics report? Read
<https://support.rstudio.com/hc/en-us/articles/205753617-Code-Diagnostics> to
find out.