Notes.txt

asciidoc --backend=xhtml11 --out-file=README.html README.asciidoc && open README.html
zip -j Linguist-0.4.zip README.html CHANGES.txt Linguist/bin/Debug/Linguist.vsix

* tex \todo should be more visible, maybe red or something
* tex section and subsection should be more visible.
* Makefile Target: ^ [^\t;\:\r\n](?: [^;\r\n]*[^;\:\r\n])? (?= \: \s* $)
* Be sure to mention that multi-line regexen don't work so well.

* Attributes are not always highlighted properly (tho the regex looks right)
* Add a directory with test files for each language.
* May want to use a weak list to avoid doing a snapshot -> doc -> extension -> language search every time
	- make sure that this cache is reset on rehup
* May want to add a shebang option to language files:
	- would need to cache this information if it is found in a snapshot
* Use reflection to init ms_elements.
* Add more elements?
* Can we log somewhere if there are errors in the static Languages ctor?
	- event log?
* Add to the studio addins site?
* Send email to freshmeat or somewhere?
* Might want to add an optional global field to default style which would cause it to be applied to all
  text documents (not just the ones with a matching language).
* Would be nice to get multi-line elements (like C-style comments) working:
	- doesn't seem possible to get the entire text 
	- usually get called with spans consisting of one line
* Would be really nice to have the styles.field file be live:
	- styles are handled by the format classes which are instantiated by the editor
	- saving these into a list when they are created and updating them later had no effect
	- so seems that we would have to somehow tell the editor that the formats have changed
* Release checklist:
	- search for TODO (in all files)
	- update the version in the readme, the assembly, and the manifest
	- make sure that the language element names listed in the readme are correct
	- install the latest version
 	- test a few different languages
	- review the readme
	- build a new readme
	- use git log --oneline > CHANGE_LOG
	- update CHANGES file
	- push changes
	- upload the zip file to githip
	- upload the zip file to the visual studio gallery
	- do a push
	- create a new branch for the release
		git checkout -b releases/version-0.3
		git push origin releases/version-0.3
		git checkout master 
		git branch -f releases/version-0.3 origin/releases/version-0.3
		git checkout releases/version-0.3
		git checkout master
	- email