{"id":4218,"date":"2022-12-20T17:39:45","date_gmt":"2022-12-20T20:39:45","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/lexgrog-ja\/"},"modified":"2022-12-20T17:39:45","modified_gmt":"2022-12-20T20:39:45","slug":"lexgrog-ja","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/lexgrog-ja\/","title":{"rendered":"LEXGROG (ja)"},"content":{"rendered":"

LEXGROG<\/h1>\n

\u00e5\u00e5<\/a>
\u00e6\u00b8\u00e5\u00bc<\/a>
\u00e8\u00aa\u00ac\u00e6<\/a>
\u00e3\u00aa\u00e3\u00e3\u00b7\u00e3\u00a7\u00e3\u00b3<\/a>
\u00e7\u00b5\u00e4\u00ba\u00e3\u00b9\u00e3\u00e3\u00bc\u00e3\u00bf\u00e3\u00b9<\/a>
\u00e4\u00be<\/a>
\u00e5\u00a6\u00e7\u00e3\u00e3\u00e3\u00e3\u00e3\u00bc\u00e3\u00bf<\/a>
\u00e9\u00a2\u00e9\u00a3\u00e9\u00a0\u00e7\u00ae<\/a>
\u00e5\u00e8<\/a>
\u00e8\u00e8<\/a>
\u00e3\u00e3\u00b0<\/a> <\/p>\n

\n

\u00e5\u00e5 <\/a> <\/h2>\n

lexgrog \u2212 \u00e3\u00e3\u00e3\u00a5\u00e3\u00a2\u00e3\u00ab\u00e3\u00e3\u00bc\u00e3\u00b8\u00e3\u00ae\u00e3\u00e3\u00e3\u00e3\u00bc\u00e6\u00e5\u00a0\u00b1\u00e3\u00e8\u00a7\u00a3\u00e9\u00e3\u00e3<\/p>\n

\u00e6\u00b8\u00e5\u00bc <\/a> <\/h2>\n

lexgrog<\/b> [\u2212m<\/b>|\u2212c<\/b>] [\u2212dfw?V<\/b>] [\u2212E<\/b> encoding<\/i>] file<\/i> …<\/p>\n

\u00e8\u00aa\u00ac\u00e6 <\/a> <\/h2>\n

lexgrog<\/b> is an implementation of the traditional \u201cgroff guess\u201d utility in lex<\/b>. It reads the list of files on its command line as either man page source files or preformatted \u201ccat\u201d pages, and displays their name and description as used by apropos<\/b> and whatis<\/b>, the list of preprocessing filters required by the man page before it is passed to nroff<\/b> or troff<\/b>, or both.<\/p>\n

If its input is badly formatted, lexgrog<\/b> will print \u201cparse failed\u201d; this may be useful for external programs that need to check man pages for correctness. If one of lexgrog<\/b>\u2019s input files is \u201c\u2212\u201d, it will read from standard input; if any input file is compressed, a decompressed version will be read automatically.<\/p>\n

\u00e3\u00aa\u00e3\u00e3\u00b7\u00e3\u00a7\u00e3\u00b3 <\/a> <\/h2>\n

\u2212d<\/b>, \u2212\u2212debug<\/b><\/p>\n

\u00e3\u00e3\u00e3\u00e3\u00b0\u00e6\u00e5\u00a0\u00b1\u00e3\u00e8\u00a1\u00a8\u00e7\u00a4\u00ba\u00e3\u00e3\u00be\u00e3\u00e3<\/p>\n

\u2212m<\/b>, \u2212\u2212man<\/b><\/p>\n

Parse input as man page source files. This is the default if neither \u2212\u2212man<\/b> nor \u2212\u2212cat<\/b> is given.<\/p>\n

\u2212c<\/b>, \u2212\u2212cat<\/b><\/p>\n

Parse input as preformatted man pages (\u201ccat pages\u201d). \u2212\u2212man<\/b> and \u2212\u2212cat<\/b> may not be given simultaneously.<\/p>\n

\u2212w<\/b>, \u2212\u2212whatis<\/b><\/p>\n

Display the name and description from the man page\u2019s header, as used by apropos<\/b> and whatis<\/b>. This is the default if neither \u2212\u2212whatis<\/b> nor \u2212\u2212filters<\/b> is given.<\/p>\n

\u2212f<\/b>, \u2212\u2212filters<\/b><\/p>\n

Display the list of filters needed to preprocess the man page before formatting with nroff<\/b> or troff<\/b>.<\/p>\n

\u2212E<\/b> encoding<\/i>, \u2212\u2212encoding<\/b> encoding<\/i><\/p>\n

Override the guessed character set for the page to encoding<\/i>.<\/p>\n

\u2212?<\/b>, \u2212\u2212help<\/b><\/p>\n

\u00e3\u00e3\u00ab\u00e3\u00e3\u00a1\u00e3\u00e3\u00bb\u00e3\u00bc\u00e3\u00b8\u00e3\u00e8\u00a1\u00a8\u00e7\u00a4\u00ba\u00e3\u00e3\u00a6\u00e7\u00b5\u00e4\u00ba\u00e3\u00e3\u00be\u00e3\u00e3<\/p>\n

\u2212\u2212usage<\/b><\/p>\n

Print a short usage message and exit.<\/p>\n

\u2212V<\/b>, \u2212\u2212version<\/b><\/p>\n

\u00e3\u00e3\u00bc\u00e3\u00b8\u00e3\u00a7\u00e3\u00b3\u00e6\u00e5\u00a0\u00b1\u00e3\u00e8\u00a1\u00a8\u00e7\u00a4\u00ba\u00e3\u00e3\u00be\u00e3\u00e3<\/p>\n

\u00e7\u00b5\u00e4\u00ba\u00e3\u00b9\u00e3\u00e3\u00bc\u00e3\u00bf\u00e3\u00b9 <\/a> <\/h2>\n\n\n\n\n
<\/td>\n\n

0<\/b><\/p>\n<\/td>\n

<\/td>\n\n

\u00e3\u00e3\u00e3\u00b0\u00e3\u00a9\u00e3\u00a0\u00e3\u00e6\u00a3\u00e5\u00b8\u00b8\u00e3\u00ab\u00e5\u00ae\u00e8\u00a1\u00e3\u00e3\u00e3\u00be\u00e3\u00e3\u00e3<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

1<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Usage error.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

2<\/b><\/p>\n<\/td>\n

<\/td>\n\n

lexgrog<\/b> failed to parse one or more of its input files.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u00e4\u00be <\/a> <\/h2>\n

$ lexgrog man.1
man.1: “man \u2212 an interface to the system reference manuals”
$ lexgrog \u2212fw man.1
man.1 (t): “man \u2212 an interface to the system reference manuals”
$ lexgrog \u2212c whatis.cat1
whatis.cat1: “whatis \u2212 display manual page descriptions”
$ lexgrog broken.1
broken.1: parse failed<\/p>\n

\u00e5\u00a6\u00e7\u00e3\u00e3\u00e3\u00e3\u00e3\u00bc\u00e3\u00bf <\/a> <\/h2>\n

mandb<\/b> (which uses the same code as lexgrog<\/b>) parses the NAME<\/b> section at the top of each manual page looking for names and descriptions of the features documented in each. While the parser is quite tolerant, as it has to cope with a number of different forms that have historically been used, it may sometimes fail to extract the required information.<\/p>\n

When using the traditional man<\/i> macro set, a correct NAME<\/b> section looks something like this:<\/p>\n

.SH NAME
foo \u2212 program to do something<\/p>\n

Some manual pagers require the \u2018\u2212\u2019 to be exactly as shown; mandb<\/b> is more tolerant, but for compatibility with other systems it is nevertheless a good idea to retain the backslash.<\/p>\n

On the left\u2212hand side, there may be several names, separated by commas. Names containing whitespace will be ignored to avoid pathological behaviour on certain ill\u2212formed NAME<\/b> sections. The text on the right\u2212hand side is free\u2212form, and may be spread over multiple lines. If several features with different descriptions are being documented in the same manual page, the following form is therefore used:<\/p>\n

.SH NAME
foo, bar \u2212 programs to do something
.br
baz \u2212 program to do nothing<\/p>\n

(A macro which starts a new paragraph, like .PP, may be used instead of the break macro .br.)<\/p>\n

When using the BSD\u2212derived mdoc<\/i> macro set, a correct NAME<\/b> section looks something like this:<\/p>\n

.Sh NAME
.Nm foo
.Nd program to do something<\/p>\n

There are several common reasons why whatis parsing fails. Sometimes authors of manual pages replace \u2018.SH NAME\u2019 with \u2018.SH MYPROGRAM\u2019, and then mandb<\/b> cannot find the section from which to extract the information it needs. Sometimes authors include a NAME section, but place free\u2212form text there rather than \u2018name \u2212 description\u2019. However, any syntax resembling the above should be accepted.<\/p>\n

\u00e9\u00a2\u00e9\u00a3\u00e9\u00a0\u00e7\u00ae <\/a> <\/h2>\n

apropos<\/i>(1), man<\/i>(1), whatis<\/i>(1), mandb<\/i>(8)<\/p>\n

\u00e5\u00e8 <\/a> <\/h2>\n

lexgrog<\/b> attempts to parse files containing .so requests, but will only be able to do so correctly if the files are properly installed in a manual page hierarchy.<\/p>\n

\u00e8\u00e8 <\/a> <\/h2>\n

The code used by lexgrog<\/b> to scan man pages was written by:<\/p>\n

Wilf. (G.Wilford@ee.surrey.ac.uk).
Fabrizio Polacco (fpolacco@debian.org).
Colin Watson (cjwatson@debian.org).<\/p>\n

Colin Watson wrote the current incarnation of the command\u2212line front\u2212end, as well as this man page.<\/p>\n

\u00e3\u00e3\u00b0 <\/a> <\/h2>\n

https:\/\/savannah.nongnu.org\/bugs\/?group=man-db<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

LEXGROG \u00e5\u00e5 \u00e6\u00b8\u00e5\u00bc \u00e8\u00aa\u00ac\u00e6 \u00e3\u00aa\u00e3\u00e3\u00b7\u00e3\u00a7\u00e3\u00b3 \u00e7\u00b5\u00e4\u00ba\u00e3\u00b9\u00e3\u00e3\u00bc\u00e3\u00bf\u00e3\u00b9 \u00e4\u00be \u00e5\u00a6\u00e7\u00e3\u00e3\u00e3\u00e3\u00e3\u00bc\u00e3\u00bf \u00e9\u00a2\u00e9\u00a3\u00e9\u00a0\u00e7\u00ae \u00e5\u00e8 \u00e8\u00e8 \u00e3\u00e3\u00b0 \u00e5\u00e5 lexgrog \u2212 \u00e3\u00e3\u00e3\u00a5\u00e3\u00a2\u00e3\u00ab\u00e3\u00e3\u00bc\u00e3\u00b8\u00e3\u00ae\u00e3\u00e3\u00e3\u00e3\u00bc\u00e6\u00e5\u00a0\u00b1\u00e3\u00e8\u00a7\u00a3\u00e9\u00e3\u00e3 \u00e6\u00b8\u00e5\u00bc lexgrog [\u2212m|\u2212c] [\u2212dfw?V] [\u2212E encoding] file … \u00e8\u00aa\u00ac\u00e6 lexgrog is an implementation of the traditional \u201cgroff guess\u201d utility in lex. It reads the list of files on its command line as either man page source files or preformatted […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[962],"tags":[964,1268,968],"class_list":["post-4218","post","type-post","status-publish","format-standard","hentry","category-1-comandos-generales","tag-964","tag-ja","tag-lexgrog"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4218","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=4218"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4218\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=4218"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=4218"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=4218"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}