From 5280f9a0cd1f9ba200422ebba65d1e0133410995 Mon Sep 17 00:00:00 2001 From: Kaz Kylheku Date: Sat, 13 Sep 2014 09:43:21 -0700 Subject: Initial. --- man2html/scripts/cgi-aux/man/man.aux | 75 +++++++ man2html/scripts/cgi-aux/man/mansearch.aux | 49 ++++ man2html/scripts/cgi-aux/man/mansearchhelp.aux | 295 +++++++++++++++++++++++++ 3 files changed, 419 insertions(+) create mode 100644 man2html/scripts/cgi-aux/man/man.aux create mode 100644 man2html/scripts/cgi-aux/man/mansearch.aux create mode 100644 man2html/scripts/cgi-aux/man/mansearchhelp.aux (limited to 'man2html/scripts/cgi-aux') diff --git a/man2html/scripts/cgi-aux/man/man.aux b/man2html/scripts/cgi-aux/man/man.aux new file mode 100644 index 0000000..e381b01 --- /dev/null +++ b/man2html/scripts/cgi-aux/man/man.aux @@ -0,0 +1,75 @@ +Content-type: text/html + + + +Manual Pages - Main Contents + + + + +

Manual Pages - Main Contents

+
+ +

Name and Section lookup

+ + +%lynx Start a query by typing an s. +You can enter a program name, possibly preceded by the section, +the directories to search (with -M) or a full name. +For example: + + +
+ +

Index of pages by name and description

+Sections: + 1. User Commands; + 2. System Calls; + 3. Library Functions; + 4. Special Files; + 5. File Formats; + 6. Games; + 7. Miscellany; + 8. Administration and Privileged Commands; + l. Postgresql Commands; + n. Tcl Commands. +

+

+

Index of pages by name only

+ 1. User Commands; + 2. System Calls; + 3. Library Functions; + 4. Special Files; + 5. File Formats; + 6. Games; + 7. Miscellany; + 8. Administration and Privileged Commands; + l. Postgresql Commands; + n. Tcl Commands; + All Sections. +

+

+ +

Manual Pages full text search

+ + +Search the full text of the Manual Pages. + + +

+

+ +The original man2html program and scripts are due to + +Richard Verhoeven and + +Michael Hamilton. +This version is from man-1.6g maintained by +Federico Lucifredi. + + diff --git a/man2html/scripts/cgi-aux/man/mansearch.aux b/man2html/scripts/cgi-aux/man/mansearch.aux new file mode 100644 index 0000000..f1d19a2 --- /dev/null +++ b/man2html/scripts/cgi-aux/man/mansearch.aux @@ -0,0 +1,49 @@ +Content-type: text/html + + + +Manual Pages - Text Search + + + + +

Manual Pages - Text Search

+ +Return to Main Contents +

+ + +%lynx Start a query by typing an s. + +Examples: +

+ +
+

+The index uses the Glimpse +(glimpse(1)) +text indexing system. Many of the glimpse +options, regular expressions, and wildcards are valid: +see the help page for a summary. +

+

+ +

+Glimpse +was developed by Udi Manber and Burra Gopal of the University of +Arizona, and Sun Wu of the National Chung-Cheng University, Taiwan. +You may contact the authors at +glimpse@cs.arizona.edu +

+The Manual Page text search interface was created for Linux by + +Michael Hamilton. + + diff --git a/man2html/scripts/cgi-aux/man/mansearchhelp.aux b/man2html/scripts/cgi-aux/man/mansearchhelp.aux new file mode 100644 index 0000000..200b509 --- /dev/null +++ b/man2html/scripts/cgi-aux/man/mansearchhelp.aux @@ -0,0 +1,295 @@ +Content-type: text/html + + + +Manual Pages - Search Help + + + + +

Manual Pages - Search Help

+ +Perform another search +
+Return to Main Contents +

+

+

+The full text index uses the Glimpse text indexing system. +The +glimpse(1) +manual page documents glimpse in full. This summary documents those +features of glimpse that are valid when searching through the manual pages. +

+

+ +

Search Options

+ +The following search options must be at the start of the search string. + +
+ +
- # +
+# is an integer between 1 and 8 +specifying the maximum number of errors +permitted in finding the approximate matches (the default is zero). +Generally, each insertion, deletion, or substitution counts as one error. +Since the index stores only lower case characters, errors of +substituting upper case with lower case may be missed. + +
-B +
+Best match mode. (Warning: -B sometimes misses matches. It is safer +to specify the number of errors explicitly.) +When -B is specified and no exact matches are found, glimpse +will continue to search until the closest matches (i.e., the ones +with minimum number of errors) +are found. +In general, -B may be slower than -#, but not by very much. +Since the index stores only lower case characters, errors of +substituting upper case with lower case may be missed. + +
-L x | x:y | x:y:z +
+A non-zero value of x limits the number of matches +that will be shown. +A non-zero value of y limits the number of man pages +that will be shown. +A non-zero valye of z will only show pages that have +less that z matches. +For example, -L 0:10 will output all matches for the first 10 files that +contain a match. + +
-F pattern +
+The -F option provides a pattern that restricts the search results to +those filenames that match the pattern. +or example, -F 8 effectively restricts matches to section 8. + +
-w +
+Search for the pattern as a word - i.e., surrounded by non-alphanumeric +characters. For example, +-w -1 car will match cars, but not characters and not +car10. +The non-alphanumeric must +surround the match; they cannot be counted as errors. +This option does not work with regular expressions. + +
-W +
+The default for Boolean AND queries is that they cover one record +(the default for a record is one line) at a time. +For example, glimpse 'good;bad' will output all lines containing +both 'good' and 'bad'. +The -W option changes the scope of Booleans to be the whole file. +Within a file glimpse will output all matches to any of the patterns. +So, glimpse -W 'good;bad' will output all lines containing 'good' +or 'bad', but only in files that contain both patterns. + +
-k +
+No symbol in the pattern is treated as a meta character. +For example, -k a(b|c)*d will find +the occurrences of a(b|c)*d whereas a(b|c)*d +will find substrings that match the regular expression 'a(b|c)*d'. +(The only exception is ^ at the beginning of the pattern and $ at the +end of the pattern, which are still interpreted in the usual way. +Use \^ or \$ if you need them verbatim.) + +
+ +

+

+ +

Patterns

+ +Glimpse +supports a large variety of patterns, including simple +strings, strings with classes of characters, sets of strings, +wild cards, and regular expressions (see LIMITATIONS). + +
+
Strings
+Strings are any sequence of characters, including the special symbols +`^' for beginning of line and `$' for end of line. +The following special characters ( +`$', + +`^', + +`*', + +`[', + +`^', + +`|', + +`(', + +`)', + +`!', + +and +`\' + +) +as well as the following meta characters special to glimpse (and agrep): +`;', + +`,', + +`#', + +`<', + +`>', + +`-', + +and +`.', + +should be preceded by `\' if they are to be matched as regular +characters. For example, \^abc\\ corresponds to the string ^abc\, +whereas ^abc corresponds to the string abc at the beginning of a +line. +
Classes of characters
+a list of characters inside [] (in order) corresponds to any character +from the list. For example, [a-ho-z] is any character between a and h +or between o and z. The symbol `^' inside [] complements the list. +For example, [^i-n] denote any character in the character set except +character 'i' to 'n'. +The symbol `^' thus has two meanings, but this is consistent with +egrep. +The symbol `.' (don't care) stands for any symbol (except for the +newline symbol). +
Boolean operations
+Glimpse + +supports an `AND' operation denoted by the symbol `;' +an `OR' operation denoted by the symbol `,', +or any combination. +For example, +glimpse 'pizza;cheeseburger' will output all lines containing +both patterns. +glimpse -F 'gnu;\.c$' 'define;DEFAULT' +will output all lines containing both 'define' and 'DEFAULT' +(anywhere in the line, not necessarily in order) in +files whose name contains 'gnu' and ends with .c. +glimpse '{political,computer};science' will match 'political science' +or 'science of computers'. +
Wild cards
+The symbol '#' is used to denote a sequence +of any number (including 0) +of arbitrary characters (see LIMITATIONS). +The symbol # is equivalent to .* in egrep. +In fact, .* will work too, because it is a valid regular expression +(see below), but unless this is part of an actual regular expression, +# will work faster. +(Currently glimpse is experiencing some problems with #.) +
Combination of exact and approximate matching
+Any pattern inside angle brackets <> must match the text exactly even +if the match is with errors. For example, <mathemat>ics matches +mathematical with one error (replacing the last s with an a), but +mathe<matics> does not match mathematical no matter how many errors are +allowed. +(This option is buggy at the moment.) +
Regular expressions
+Since the index is word based, a regular expression must match +words that appear in the index for glimpse to find it. +Glimpse first strips the regular expression from all non-alphabetic +characters, and searches the index for all remaining words. +It then applies the regular expression matching algorithm to the +files found in the index. +For example, glimpse 'abc.*xyz' will search the index +for all files that contain both 'abc' and 'xyz', and then +search directly for 'abc.*xyz' in those files. +(If you use glimpse -w 'abc.*xyz', then 'abcxyz' will not be found, +because glimpse +will think that abc and xyz need to be matches to whole words.) +The syntax of regular expressions in glimpse is in general the same as +that for agrep. The union operation `|', Kleene closure `*', +and parentheses () are all supported. +Currently '+' is not supported. +Regular expressions are currently limited to approximately 30 +characters (generally excluding meta characters). Some options +(-d, -w, -t, -x, -D, -I, -S) do not +currently work with regular expressions. +The maximal number of errors for regular expressions that use '*' +or '|' is 4. (See LIMITATIONS.) + +
+ +
+ +

Limitations

+ +The index of glimpse is word based. A pattern that contains more than +one word cannot be found in the index. The way glimpse overcomes this +weakness is by splitting any multi-word pattern into its set of words +and looking for all of them in the index. +For example, glimpse 'linear programming' will first consult the index +to find all files containing both linear and programming, +and then apply agrep to find the combined pattern. +This is usually an effective solution, but it can be slow for +cases where both words are very common, but their combination is not. +

+ +As was mentioned in the section on PATTERNS above, some characters +serve as meta characters for glimpse and need to be +preceded by '\' to search for them. The most common +examples are the characters '.' (which stands for a wild card), +and '*' (the Kleene closure). +So, "glimpse ab.de" will match abcde, but "glimpse ab\.de" +will not, and "glimpse ab*de" will not match ab*de, but +"glimpse ab\*de" will. +The meta character - is translated automatically to a hyphen +unless it appears between [] (in which case it denotes a range of +characters). +

+ +The index of glimpse stores all patterns in lower case. +When glimpse searches the index it first converts +all patterns to lower case, finds the appropriate files, +and then searches the actual files using the original +patterns. +So, for example, glimpse ABCXYZ will first find all +files containing abcxyz in any combination of lower and upper +cases, and then searches these files directly, so only the +right cases will be found. +One problem with this approach is discovering misspellings +that are caused by wrong cases. +For example, glimpse -B abcXYZ will first search the +index for the best match to abcxyz (because the pattern is +converted to lower case); it will find that there are matches +with no errors, and will go to those files to search them +directly, this time with the original upper cases. +If the closest match is, say AbcXYZ, glimpse may miss it, +because it doesn't expect an error. +Another problem is speed. If you search for "ATT", it will look +at the index for "att". Unless you use -w to match the whole word, +glimpse may have to search all files containing, for example, "Seattle" +which has "att" in it. +

+ +There is no size limit for simple patterns and simple patterns +within Boolean expressions. +More complicated patterns, such as regular expressions, +are currently limited to approximately 30 characters. +Lines are limited to 1024 characters. +Records are limited to 48K, and may be truncated if they are larger +than that. +The limit of record length can be +changed by modifying the parameter Max_record in agrep.h. +

+ +Glimpseindex does not index words of size > 64. +  + +

+ + -- cgit v1.2.3