Skip to content

fix typo #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
naterajj wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix typo #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions manuscript/why_indent.Rmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,11 @@ At the Use R! 2018 meeting in Brisbane, Australia, Jenny Bryan gave a wonderful

As mentioned previously in this book, my general indenting policy for R code is to use 8 spaces per indent. In my experience, people tend to find this a rather extreme indentation policy, with maybe 4 spaces being at the outer limit of what they could imagine. But I’ve been using 8 spaces for a long time now and I’ve found that it has a number of benefits.

First off, I did not make up the 8 space indent. I got it from the [Linux kernal coding style document](https://www.kernel.org/doc/Documentation/process/coding-style.rst). Chapter 1 says:
First off, I did not make up the 8 space indent. I got it from the [Linux kernel coding style document](https://www.kernel.org/doc/Documentation/process/coding-style.rst). Chapter 1 says:

> Tabs are 8 characters, and thus indentations are also 8 characters. There are heretic movements that try to make indentations 4 (or even 2!) characters deep, and that is akin to trying to define the value of PI to be 3.

I've found the Linux kernal coding style to be pretty useful for my R programming, but a lot of it is C-specific and so not relevant. Nevertheless, it's worth a quick peruse.
I've found the Linux kernel coding style to be pretty useful for my R programming, but a lot of it is C-specific and so not relevant. Nevertheless, it's worth a quick peruse.

Personally, I've found 8 spaces is good for my aging eyes. I think my rule is that the appropriate number of spaces of indentation is proportional to the square of my age (I'm still working on that model though). At this point, code with a 2 space indent is indistinguishable from flush left.

Expand Down
4 changes: 2 additions & 2 deletions manuscript/why_indent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ spaces for a long time now and I’ve found that it has a number of
benefits.

First off, I did not make up the 8 space indent. I got it from the
[Linux kernal coding style
[Linux kernel coding style
document](https://www.kernel.org/doc/Documentation/process/coding-style.rst).
Chapter 1 says:

Expand All @@ -26,7 +26,7 @@ Chapter 1 says:
> 2!) characters deep, and that is akin to trying to define the value of
> PI to be 3.

I've found the Linux kernal coding style to be pretty useful for my R
I've found the Linux kernel coding style to be pretty useful for my R
programming, but a lot of it is C-specific and so not relevant.
Nevertheless, it's worth a quick peruse.

Expand Down