Added history and license files. Converted README to RDoc format.

Author: AlanQuatermain

History.rdoc

@@ -0,0 +1,13 @@
+=== 0.2.0 / 2009-11-15
+* New indentation increase/decrease rules:
+  * Case statements decrease and increase (they pop their own line back by one indent without affecting either prior or following line).
+  * Regular braces now increase/decrease indent automatically.
+* Regular braces now act as folding markers for multi-line 'const ( ... )' declarations.
+* Code-folding matches on curly braces are now more conservative-- before, they could match characters beyond newlines.
+* Built-in storage types are now matched properly.
+* Variable initialization is FINALLY matching correctly. Should work for every style & number of variables, even in-line in loop statements.
+* Matches exported variable names correctly (i.e. those beginning with an uppercase letter).
+* Dot-accessed variable match no longer consumes the preceding '.' character.
+ 
+=== 0.1.0 / 2009-11-14
+* Initial Revision

LICENSE

@@ -0,0 +1,12 @@
+Copyright (c) 2009, Jim Dovey
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+- Neither the name of the copyright holder nor the names of the software's contributors may be used to endorse or promote products derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+Portions based on Allan Odgaard's C bundle for TextMate.

README

@@ -0,0 +1,34 @@
+= Go
+(a TextMate language bundle)
+
+=== Features
+The bundle here implements a language syntax, some snippets, and a 'Run' command for the Go language (http://golang.org).
+
+At present there are still a couple of odd things to clear up. If anyone can suggest how to change the Run script to stop after any errors compiling or linking, and to not output empty blocks for those steps if all went well, I would be very grateful.
+
+=== Snippets
++imp+::    sets up an import statement with optional alternative name.
++func+::   creates a function declaration with tab-stops for name, parameters, and return types.
++tfunc+::  creates a function as 'func' but adds the variable declaration needed to attach the function to a type (like a class method).
++type+::   initializes a type declaration for you, with name and variable type as tab-stops.
++struct+:: lays out a structure declaration (use 'type' first to name your structure) with a tab stop on a sample member variable.
++main+::   creates a plain 'main()' function for you.
++for+::    lays out a standard for loop, with tab stops for count, variable name, and loop-end action.
++if+::     lays out a plain if statement, with curly braces, tab stop on the condition. This is here because an if in Go MUST use braces it seems, and this is as good a way as any to force myself (and others) to remember that.
+
+=== Compiling and Running
+The Run() function will run 6g on your source file, then run 6l on the new <name>.6 file, then run the resulting 6.out file. All files will be created in the same folder as the source file. It doesn't do anything about building packages yet-- that's something I'll add later on. In the meantime, to build a package archive (or append new .6 files to an existing package archive) you would use:
+
+> 6g myfile.go
+> gopack rg <archive>.a myfile.6 ...
+
+<archive> is the name for your archive file, and you can specify multiple .6 files to be appended to that archive. So for instance:
+
+> 6g my_io.go my_file.go my_echo.go my_cat.go
+> gopack rg my_stuff.a my_io.6 my_file.6 my_echo.6 my_cat.6
+
+=== Contact Information
+
+You can contact me through github, or you can ping me on Twitter as 'alanQuatermain'.
+
+Happy coding :)