Multiple fixes (#94)

* attribute and type fixes.

* rework attributes

* fix ints within attribute

* type definition within attributes

* fix strings in attribute

* fix case for string include

* rescope types and attributes.

* correct comments inline with attribute

* rescope variables.

* change end captures for attribute

* fix double quoted strings.

* rescope variable token for cosmetic reasons

* first pass at fixing indices

* fix types and indices

* fix digits in types (removed by accident.)

* fix new line between ) and ] on attribute.

* restructure for CI

* setup build scripts

* add spec file

* build script tweaks

* rescope comments

* add build file to test step

* add self to attribute

* advanced function tests.

* better descriptions for automatic tests

* make the build script pretty

* appveyor -> run tests

* fix section name

* fix atom path variable

* add exit condition

* class specs

* fix variable scope

* variable scoping - closing brace

* correct hashtable scopes

* rescope numerics.

* remove redundancy.

* missed a numeric scope.

* fix range operator for negative numbers

* scope array tokens

* correct interpolation parens scope

* scriptblock scopes

* the big spec file... first half.

* fix xml typo

* fix xml typo

* stop parameter names that match keywords from highlighting

* add default keyword

* tweak function keyword scopes.

* Make build.ps1 crossplatform

* stop function end capture from clobbering other scopes

* more scoping in big test file.

* remove dependence on build.ps1

* remove dependence on build.ps1

* comments between function def and K&R bracket

* Update readme.

* correct subexpression punctuation scopes.

* finish big spec file.

* change test to a switch param in build.ps1

* newline at EOF

* fix email addresses within strings

Author: omniomi

.gitignore

@@ -1,2 +1,5 @@
 syntaxes/
-tools/node_modules/
+grammars/
+node_modules/
+atom/
+atom.zip

CONTRIBUTING.md

@@ -34,4 +34,4 @@ Fixing issues also does not require a lot of administrative work. The basic step
 
 ## Reviews
 
-We are using GitHub's internal capabilities for our code reviews. Either we, the EditorSyntax team, or you, the community, can review the changes and add comments. The author of the pull request can then go through all issues, fix them and add commits to his branch, which will show up in the pull request. When all issues are fixed and there is nothing else to do, we will gladly merge your pull request.
+We are using GitHub's internal capabilities for our code reviews. Either we, the EditorSyntax team, or you, the community, can review the changes and add comments. The author of the pull request can then go through all issues, fix them and add commits to his branch, which will show up in the pull request. When all issues are fixed and there is nothing else to do, we will gladly merge your pull request.