| author | Lorenzo Bettini <bettini@dsi.unifi.it> | 2008年07月17日 18:47:52 +0000 |
|---|---|---|
| committer | Lorenzo Bettini <bettini@dsi.unifi.it> | 2008年07月17日 18:47:52 +0000 |
| commit | a57f014e18d763cd60cbacc09ff0c8429abffb89 (patch) | |
| tree | f0d1ef20da1c92e5471ebfcdb6757e077cdad9b6 /doc/check-regexp.1 | |
| parent | 5a1956aca3266d93922f5e69c605e611f77c32ef (diff) | |
| download | src-highlite-a57f014e18d763cd60cbacc09ff0c8429abffb89.tar.gz | |
| -rwxr-xr-x | doc/check-regexp.1 | 35 |
diff --git a/doc/check-regexp.1 b/doc/check-regexp.1 new file mode 100755 index 0000000..040c4a1 --- /dev/null +++ b/doc/check-regexp.1 @@ -0,0 +1,35 @@ +.TH CHECK-REGEXP "1" "June 2008" "check-regexp 2.9" "User Commands" +.SH NAME +check-regexp \- test regular expressions from the command line +.SH SYNOPSIS +.B check-regexp +\fI'regular expression' 'string1' 'string2' \fR... +.SH DESCRIPTION +check\-regexp (GNU Source\-highlight) +.PP +You simply pass as the first command line argument the regular expression and +then the strings you want to try to match. +.br +It is crucial, in order to avoid shell substitutions, to enclose both the +expression and the strings in single quotes. +.sp +The program then prints some information about the possibly successful +matching. +.br +In the output the what[0] part represents the whole match, and the what[i] +part represents the i-th marked subexpression that matched. +.sp +The program also prints possible prefix and suffix. +.SH OPTIONS +This program follows the usual GNU command line syntax, with long +options starting with two dashes (`-'). +A summary of options is included below. +.TP +\fB\-h\fR, \fB\-\-help\fR +Print help and exit +.TP +\fB\-V\fR, \fB\-\-version\fR +Print version and exit +.SH AUTHOR +check-regexp was written by Lorenzo Bettini <www.lorenzobettini.it>. +This man page was written by Cesare Tirabassi <norsetto@ubuntu.com>.
\ No newline at end of file |