internal changes to paragrep

Author: ildar-shaimordanov

README.md

@@ -69,13 +69,13 @@ Later I decided to implement it as the standalone script adding more functionali
 Each log entry in log files usually begins with the timestamp in the generalized numeric form *date time*, which can be covered by the pattern without reflecting on which date format has been used to output dates:
 
 ```bash
-paragrep -Pp '^\d+/\d+/\d+ \d+:\d+:\d+' PATTERN FILENAME
+paragrep -Pp '^\d+[/-]\d+[/-]\d+ \d+:\d+:\d+' PATTERN FILENAME
 ```
 
 Also the aliases for parsing log files and INI-like configuration files:
 
 ```bash
-alias lgrep="paragrep -Pp '^\d+/\d+/\d+ \d+:\d+:\d+'"
+alias lgrep="paragrep -Pp '^\d+[/-]\d+[/-]\d+ \d+:\d+:\d+'"
 alias cgrep="paragrep -Pp '^(#@ |#-> )?\['"
 ```
 

TODO

@@ -0,0 +1,11 @@
+# paragrep
+
+Output control
+
+--color={never|always|auto}
+
+Context control
+
+-B, --before-context=NUMBER
+-A, --after-context=NUMBER
+-C, --context=NUMBER

perl/paragrep

@@ -133,11 +133,11 @@ The following example demonstrates the customized paragraph definition
 for parsing log files. Usually, applications producing log files write
 one log entry per one line. Somethimes applications (especially written
 in Java) produce multiline log entries. Each log entry begins with the
-timestamp in the generalized form C<date time>, which can be covered by
-the pattern C<\d+/\d+/\d+ \d+:\d+:\d+> without reflecting on which date
-format has been used to output dates:
+timestamp in the generalized form C<date time>, which can be covered
+by the pattern C<^\d+[/-]\d+[/-]\d+ \d+:\d+:\d+> without reflecting on
+which date format has been used to output dates:
 
-    paragrep -Pp '^\d+/\d+/\d+ \d+:\d+:\d+' PATTERN FILENAME
+    paragrep -Pp '^\d+[/-]\d+[/-]\d+ \d+:\d+:\d+' PATTERN FILENAME
 
 =head2 Example
 
@@ -180,7 +180,7 @@ perlre(1)
 
 =head1 COPYRIGHT
 
-Copyright 2017-2021, Ildar Shaimordanov
+Copyright 2017-2022, Ildar Shaimordanov
 
   MIT License