keyword_search 1.0.0 → 1.0.1

data/README.txt

@@ -23,8 +23,7 @@ Development Roadmap:
 
 == SYNOPSIS:
 
-Here's an example of usage from Rails.  
-* Note that the library is generic, and could presumably be used for any Ruby project.
+Here's an example of usage from Rails (though the library is generic, and could presumably be used for any Ruby project)
 
   # Some variables to build up
   clauses = []
@@ -32,6 +31,7 @@ Here's an example of usage from Rails.
 
   # Search a string, defining the supported keywords and building up
   # the variables in the associated closures
+  
   KeywordSearch.search('account has:attachment since:2006-12-03') do |with|
 
     with.default_keyword :title

data/Rakefile

@@ -5,7 +5,7 @@ require 'hoe'
 require './lib/keyword_search.rb'
 
 Hoe.new('keyword_search', KeywordSearch::VERSION) do |p|
-  p.rubyforge_name = 'keyword_search'
+  p.rubyforge_name = 'codefluency'
   p.summary = 'Generic support for extracting GMail-style search keywords/values from strings'
   p.description = p.paragraphs_of('README.txt', 2..5).join("\n\n")
   p.url = p.paragraphs_of('README.txt', 0).first.split(/\n/)[1..-1]

data/lib/keyword_search.rb

@@ -7,7 +7,7 @@ end
 
 module KeywordSearch
   
-  VERSION = '1.0.0'
+  VERSION = '1.0.1'
   
   class << self
     def search(input_string, definition=nil, &block)

metadata

@@ -3,14 +3,14 @@ rubygems_version: 0.9.0
 specification_version: 1
 name: keyword_search
 version: !ruby/object:Gem::Version 
-  version: 1.0.0
+  version: 1.0.1
 date: 2007-01-08 00:00:00 -07:00
 summary: Generic support for extracting GMail-style search keywords/values from strings
 require_paths: 
 - lib
 email: bruce@codefluency.com
 homepage: "    http://codefluency.rubyforge.org/keyword_search"
-rubyforge_project: keyword_search
+rubyforge_project: codefluency
 description: "== FEATURES/PROBLEMS:  The library features a very simple, easy-to-use API. * Define handlers for supported keywords with blocks * Define the default keyword (values not part of a keyword/value pair)  Various notes: * Quoted values are supported. * Input is automatically downcased (both keywords and values should be assumed to be in lowercase)  Development Roadmap: 1.1:: Expand supported character set for keywords and values (currently supports a-z) 2.0:: Add negation and grouping (will break API backwards compatibility)  == SYNOPSIS:"
 autorequire: 
 default_executable: