Skip to content
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.

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

Ch2: code editor (move detailed content to wiki) #391

Open
mariaruth opened this issue Feb 20, 2020 · 0 comments
Open

Ch2: code editor (move detailed content to wiki) #391

mariaruth opened this issue Feb 20, 2020 · 0 comments
Assignees
Labels
wiki Needs Wiki update

Comments

@mariaruth
Copy link
Contributor

This feels overly detailed in the flow of the chapter. I recommend keeping the general point about using an external editor but moving the below content to a wiki article and linking to that here.

If you are working in R, \textbf{RStudio} is the typical choice.\sidenote{ \url{https://www.rstudio.com}} For Stata, the built-in do-file editor is the most widely adopted code editor, but \textbf{Atom}\sidenote{\url{https://atom.io}} and \textbf{Sublime}\sidenote{\url{https://www.sublimetext.com}} can also be configured to run Stata code externally, while offering great code accessibility and quality features. (We recommend setting up and becoming comfortable with one of these.) For example, these editors can access an entire directory -- rather than a single file -- which gives you access to directory views and file management actions, such as folder management, Git integration, and simultaneous work with other types of files, without leaving the editor.

https://github.com/worldbank/d4di/blob/8b98e52c899291a674ce23ea3174fdc4d349126d/chapters/planning-data-work.tex#L260

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wiki Needs Wiki update
Projects
None yet
Development

No branches or pull requests

3 participants