<commit_before>﻿asciidoc --backend=xhtml11 --out-file=README.html README.asciidoc && open README.html
zip -j Linguist-0.3.zip Linguist/README.html Linguist/bin/Debug/Linguist.dll Linguist/bin/Debug/Linguist.vsix Linguist/bin/Debug/extension.vsixmanifest

* Release checklist:
	- push changes
	- upload a new vsix file
	- 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
	- email

* 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 a new vsix file
	- 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
	- email
	<commit_msg>Relased version 0.4<commit_after>﻿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

* Release checklist:
	- upload the zip file to githip
	- upload the zip file to the visual studio gallery
	- 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
	- do a push
	- email

* 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
	- 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
	- do a push
	- email
	
{'fraction_non_alphanumeric': 0.05451772779260389, 'fraction_numerical': 0.009531071292413268, 'mean_word_length': 3.2076984763432237, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 11, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6041044', 'n_tokens_mistral': 1572, 'n_tokens_neox': 1452, 'n_words': 741}