gryf/pentadactyl-pm
1
0
Fork 0
mirror of https://github.com/gryf/pentadactyl-pm.git synced 2026-03-09 23:55:44 +01:00
Code Issues Projects Releases Wiki Activity

Remove vague and untrue coding style recommendations.

Browse Source
This commit is contained in:
Doug Kearns
2010-10-22 16:14:20 +11:00
parent b009825530
commit 76549faacc
1 changed files with 0 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
HACKING
View File

@@ -19,15 +19,6 @@ important, please ask.
In general: Just look at the existing source code! In general: Just look at the existing source code!
We try to target experienced JavaScript developers who do not
necessarily need to have a good understanding of Pentadactyl's source
code, nor necessarily understand in-depth concepts of other
languages like Lisp or Python. Therefore, the coding style should
feel natural to any JavaScript developer. Of course, this does not
mean, you have to avoid all new JavaScript features like list
comprehension or generators. Use them, when they make sense, but
don't use them when the resulting code is hard to read.
=== The most important style issues are: === === The most important style issues are: ===
* Use 4 spaces to indent things, no tabs, not 2, nor 8 spaces. If you use Vim, * Use 4 spaces to indent things, no tabs, not 2, nor 8 spaces. If you use Vim,