extra fudge can be added to autogrow input via .VS-search .ui-autocomplete-input{ min-width: 0px; }
added ability to specify facetAutocompleteMinLength to VS.init.  Defaults to 1 as previously did.  Setting to zero causes facet autosuggest to pop without entering anything and makes facets more discoverable.
fix for bug in IE7 & 8 where reset events were getting fired before autocomplete had been set up on on the facet.  Note: I'm sure that this has something to do specifically with the pathable use of visualsearch.js and I'm not sure it applies to everyone.
Allow * at end of word for autocomplete
Rebuild dist
Merge branch 'master' of github.com:documentcloud/visualsearch

* 'master' of github.com:documentcloud/visualsearch:
  adding new build artifacts
  adding toLowerCase statements to all of the places in search_query.js where we compare categories to user input. This seemed to make sense given that it's possible for the user to enter either upper or lower case into the autocomplete.
  Added handling for Home and End keys
Merge branch 'master' into littlebee

* master:
  adding new build artifacts
  adding toLowerCase statements to all of the places in search_query.js where we compare categories to user input. This seemed to make sense given that it's possible for the user to enter either upper or lower case into the autocomplete.
  Added handling for Home and End keys
  Docs + Build
  Adding multi-word categories. Ex: "U.S. State": "New York". Closes #53.
  Add option to set the default/remainder facet
  No need to go through an anonymous function indirection since renderFacets is using _.bind to call renderFacet
  Building for new defense against jQuery UI CSS. Fixes #46.
  Adding defensive styling to combat jQuery UI CSS.
  Bumping version to 0.2.2, new build and docs.
  Adding options.preserveMatches to documentation. Bumping version to 0.2.2.
  Adding example that shows how to set the search box value with a raw string.
  Selecting the remaining adjacent facet after another facet is removed. This rollbacks a couple lines from issue #49.
  Handle programmatic alterations of searchQuery (the facets collection)
  Improve parsing of free text in initial query
  Correctly parse unquoted 1-character categories
  Extract search regexps into text constants
  Added 'preserveMatches' to prevent matching facet values against search term
  On autocomplete 'create' we set the z-index of the input to auto, which solves show the input in modal dialogs not created in jQuery-UI. Twitter Bootstrap is a good example of where this issue would come up.
  On autocomplete 'create' we set the z-index of the input to auto, which solves show the input in modal dialogs not created in jQuery-UI. Twitter Bootstrap is a good example of where this issue would come up.

Conflicts:
	build-min/visualsearch.js
	build-min/visualsearch.js.gz
	build/visualsearch.js
	lib/js/views/search_input.js
	lib/js/visualsearch.js
Merge branch 'littlebee'

* littlebee:
  Rebuild dist
  Allow * at end of word for autocomplete
  fix for bug in IE7 & 8 where reset events were getting fired before autocomplete had been set up on on the facet.  Note: I'm sure that this has something to do specifically with the pathable use of visualsearch.js and I'm not sure it applies to everyone.
  added ability to specify facetAutocompleteMinLength to VS.init.  Defaults to 1 as previously did.  Setting to zero causes facet autosuggest to pop without entering anything and makes facets more discoverable.
  extra fudge can be added to autogrow input via .VS-search .ui-autocomplete-input{ min-width: 0px; }
Cleaning up min length autocomplete patch.