regex_replace 1.0.1 → 1.0.2

data/History.txt

@@ -1,3 +1,9 @@
+=== 1.0.2 / 2008-12-06
+
+* 1 minor enhancements to the documentation
+
+  * Cleaned README
+
 === 1.0.1 / 2008-06-29
 
 * 1 minor enhancement

data/README.txt

@@ -10,36 +10,38 @@ to appear in the replacement text.
 
 == FEATURES/PROBLEMS:
 
-<pre>usage: rr [options] find replace [filenames]
-       rr [options] s/find/replace/ [filenames]
-       rr [options] find
-  find      - a regular expression to be run on the entire file as one string
-              the final usage defaults the replacement to the empty string
-  replace   - replacement text, \1-\9 and metachars (\n, etc.) are allowed
-  filenames - names of the input files to be parsed, if blank uses STDIN
+  usage: rr [options] find replace [filenames]
+         rr [options] s/find/replace/ [filenames]
+         rr [options] find
+    find      - a regular expression to be run on the entire file as one string
+                the final usage defaults the replacement to the empty string
+    replace   - replacement text, \1-\9 and metachars (\n, etc.) are allowed
+    filenames - names of the input files to be parsed, if blank uses STDIN
+    
+  options:
+    --line or -l    process line by line instead of all at once (not default)
+    --case or -c    makes the regular expression case sensitive (not default)
+    --global or -g  process all occurrences in the text (default)
+    --modify or -m  changes will directly modify the original file (not default)
   
-options:
-  --line or -l    process line by line instead of all at once (not default)
-  --case or -c    makes the regular expression case sensitive (not default)
-  --global or -g  process all occurrences in the text (default)
-  --modify or -m  changes will directly modify the original file (not default)
-
-negated options are done by adding 'not' or 'n' in switches like so:
-  --notline or -nl
+  negated options are done by adding 'not' or 'n' in switches like so:
+    --notline or -nl
+  
+  special note:
+    When using bash, if you want backslashes in the replace portion make sure
+    to use the multiple argument usage with single quotes for the replacement.
 
-special note:
-  When using bash, if you want backslashes in the replace portion make sure
-  to use the multiple argument usage with single quotes for the replacement.
-</pre>
 
 == SYNOPSIS:
 
 Replace all a's with e's
-rr s/a/e/ file
-rr a e file
+
+  rr s/a/e/ file
+  rr a e file
 
 Doubles the last character on each line and doubles the newline.
-rr "(.)\n" "\1\1\n\n" file
+
+  rr "(.)\n" "\1\1\n\n" file
 
 == REQUIREMENTS:
 

data/lib/rr.rb

@@ -1,3 +1,3 @@
 class Rr
-  VERSION = '1.0.1'
+  VERSION = '1.0.2'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: regex_replace
 version: !ruby/object:Gem::Version 
-  version: 1.0.1
+  version: 1.0.2
 platform: ruby
 authors: 
 - Joseph Pecoraro
@@ -9,18 +9,18 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2008-06-29 00:00:00 -04:00
+date: 2008-12-06 00:00:00 -05:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: hoe
-  type: :runtime
+  type: :development
   version_requirement: 
   version_requirements: !ruby/object:Gem::Requirement 
     requirements: 
     - - ">="
       - !ruby/object:Gem::Version 
-        version: 1.6.0
+        version: 1.8.2
     version: 
 description: A multi-line search and replace utility that uses Ruby regular expressions for searching and allows back references to  captured groups from the pattern to appear in the replacement text.
 email: 
@@ -64,7 +64,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 
 rubyforge_project: bogojoker
-rubygems_version: 1.2.0
+rubygems_version: 1.3.1
 signing_key: 
 specification_version: 2
 summary: A multi-line search and replace utility that uses Ruby regular expressions for searching and allows back references to  captured groups from the pattern to appear in the replacement text.