-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add section on editors/IDEs #154
Comments
How many editors is there? I guess if we focus only on first "5" we can stick to current approach (each has its own section just like Vim and Sublime). JetBrains IDEs are commercial (in a way you can not use it for free like Sublime with nag) except educational license, which is for free. I mainly use, Visual Studio Code, Sublime, JetBrains (PyCharm + PHPStorm) and of course Vim on server side. I have tried Atom but VSC is better and I don't know any other editors 🤣 (emacs rings a bell but never used it same with nano). |
@Kyslik Yes, that's a good idea. Maybe this guide is not the proper place to tell people about Emacs ;) Let's stick with the top ~5 popular. We could then have
I can do IntelliJ and Atom, could you write a section on Visual Studio Code then @Kyslik? (I have never used it) This would also fix #143. |
Yes, I am planning on doing some work for this repo since I am still on Yosemite and soon (not a clue when) I will upgrade to the latest, and when that comes I will write about PHP (fix for #56) and many more things that may include VSC. Setting up VSC, just like with Sublime, strongly depends on what is person working with, is it a JavaScript user, maybe Python girl etc. I may cover my field: Python, JavaScript, PHP and markdown. |
Related to #143, tagging so the issues get linked |
I'm Submitting a ...
Tool/Language/etc
It would be awesome with a section of popular editors and IDEAs. This could include everything from emacs to IntelliJ and each section could have information about plugins etc.
Thoughts?
We decided to do it, here's what we need to do:
The text was updated successfully, but these errors were encountered: