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

Recommend Atom as editor #67

Closed
katrinleinweber opened this issue Nov 4, 2018 · 5 comments
Closed

Recommend Atom as editor #67

katrinleinweber opened this issue Nov 4, 2018 · 5 comments

Comments

@katrinleinweber
Copy link
Contributor

katrinleinweber commented Nov 4, 2018

We currently recommend Notepad++ to Windows users and mention Atom only briefly. Because of its Teletype capability and integration with GitHub Desktop, how about we recommend it specifically?

PS: GitHub Desktop could also be somewhat central goal for Library Carpentry to move towards, because it brings the Git Bash with it as well, and there is a derivative lesson.

@drjwbaker
Copy link

Just flagging that we've had an argument in the past about Atom LibraryCarpentry/librarycarpentry.github.io#24 tl;dr: instructors have reported the download overhead and cognitive overload of atom to be a problem.

@libcce
Copy link
Contributor

libcce commented Nov 5, 2018

Thanks @drjwbaker! This is probably something for the new Maintainers to revisit and possibly discuss. Which reminds me, I really need to prompt the groups to meet!

@drjwbaker
Copy link

Good idea. For what it is worth, I think this should be more about getting across why use a text editor than which text editor to use.

@ccronje
Copy link
Contributor

ccronje commented May 5, 2019

@libcce recommends closing this issue and creating a new issue as per @drjwbaker's comment 'add section on why use a text editor'. Would you like to do that @sharilaster @ppival @antonangelo ? It would be a good one to label mozsprint too.

As well as the tools listed here, @libcce recommends noting https://regexr.com/, brackets.io, Atom.

@libcce
Copy link
Contributor

libcce commented May 21, 2019

Thanks @ccronje! I've created #98.

@libcce libcce closed this as completed May 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants