New -msg_op opcode "parse_bulk"
This commit is contained in:
@ -9,7 +9,7 @@
|
||||
.\" First parameter, NAME, should be all caps
|
||||
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
.\" other parameters are allowed: see man(7), man(1)
|
||||
.TH XORRISO 1 "Version 1.2.5, Dec 14, 2012"
|
||||
.TH XORRISO 1 "Version 1.2.5, Dec 16, 2012"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@ -4479,8 +4479,9 @@ If text is not empty it will get put out on "M" channel each time
|
||||
\fB\-msg_op\fR opcode parameter_text
|
||||
This command shall facilitate extraction of particular information from
|
||||
the message output of other commands. It gives access to the C API function
|
||||
Xorriso_parse_line and to the message sieve that is provided by the C API.
|
||||
Please refer to their description in file xorriso.h.
|
||||
Xorriso_parse_line() and to the message sieve that is provided by the C API.
|
||||
Please refer to their descriptions in file xorriso.h.
|
||||
Further it helps to interpret the severity codes of info messages.
|
||||
.br
|
||||
Intended users are frontend programs which operate xorriso in dialog mode.
|
||||
.br
|
||||
@ -4552,6 +4553,19 @@ The next line tells the number of strings. Each string begins by a line that
|
||||
tells the number of lines of the string. Then follow these lines. They are to
|
||||
be concatenated with a newline character inbetween each of them.
|
||||
.br
|
||||
\fBparse_bulk\fR
|
||||
.br
|
||||
Like "parse", but with the fifth parameter word being number_of_input_texts
|
||||
rather than number_of_input_lines. Each input text has to be preceded by
|
||||
a line that tells number_of_input_lines as with "parse".
|
||||
Then come the announced number of text lines.
|
||||
.br
|
||||
All input texts will be read before printing of result lines begins.
|
||||
This consumes memory in xorriso. So the number_of_input_texts should not
|
||||
be extremely high. On the other hand, large transactions of command,
|
||||
input texts, and results are desirable if connection latency is an
|
||||
issue.
|
||||
.br
|
||||
\fBcompare_sev\fR
|
||||
.br
|
||||
The parameter_text should contain two comma separated severity texts as
|
||||
|
Reference in New Issue
Block a user