libburnia/legacy
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

New commands -x, -list_arg_sorting

Browse Source
This commit is contained in:
Thomas Schmitt
2012-01-31 13:04:28 +00:00
parent 55709b42e5
commit f848062bf7
12 changed files with 540 additions and 87 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
libisoburn/trunk/xorriso/xorriso.texi
View File

@ -50,7 +50,7 @@
@c man .\" First parameter, NAME, should be all caps
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
@c man .\" other parameters are allowed: see man(7), man(1)
@c man .TH XORRISO 1 "Version 1.2.1, Jan 27, 2012"
@c man .TH XORRISO 1 "Version 1.2.1, Jan 31, 2012"
@c man .\" Please adjust this date whenever revising the manpage.
@c man .\"
@c man .\" Some roff macros, for reference:
@ -591,7 +591,10 @@ only on GNU/Linux and FreeBSD, where they are known as extattr.
@c man .B Command processing:
@c man .br
Commands are either actions which happen immediately or settings which
influence following actions. So their sequence does matter.
influence following actions. So their sequence does matter, unless they are
given as program arguments and option
@strong{-x}
is among them.
@*
@cindex List delimiter, _definiton
Commands consist of a command word,
@ -729,6 +732,7 @@ the dashes of the emulated options are mandatory.
Normally any number of leading dashes is ignored with command words and
inner dashes are interpreted as underscores.
@menu
* ArgSort:: Execution order of program arguments
* AqDrive:: Aquiring source and target drive
* Loading:: Influencing the behavior of image loading
* Insert:: Inserting files into ISO image
@ -752,7 +756,44 @@ inner dashes are interpreted as underscores.
* Frontend:: Support for frontend programs via stdin and stdout
@end menu
@c man .TP
@node AqDrive, Loading, Options, Options
@node ArgSort, AqDrive, Options, Options
@section Execution order of program arguments
@c man .B Execution order of program arguments:
@c man .PP
By default the program arguments of a xorriso run are interpreted as a
sequence of commands which get performed exactly in the given order.
This requires the user to write commands for desired settings before the
commands which shall be influenced by those settings.
@*
Many other programs allow to hand over options as program arguments
in an arbitrary sequence and perform settings and actions in a sequence
of their own discretion. xorriso provides an option to enable such a behavior
at the cost of losing freedom of expression.
@table @asis
@sp 1
@c man .TP
@item -x
@kindex -x enables automatic execution order of options
@cindex Automatic execution order, of options, -x
Enable automatic sorting of program arguments to a sequence that most likely
makes some sense. This command may be given at any position among the commands
which are handed over as program arguments.
@*
It works only if it is given as program argument. I.e. not
in startup files. not with -options_from_file, not in dialog mode.
@c man .TP
@item -list_arg_sorting
@kindex -list_arg_sorting prints sorting order of -x
@cindex Sorting order, for -x, -list_arg_sorting
List all xorriso commands in the order which applies if option -x is in effect.
@*
This list may also be helpful without -x, for a user who ponders over the
sequence in which to put commands. Deviations from the sorting order may
well make sense, though.
@end table
@c man .PP
@c man .TP
@node AqDrive, Loading, ArgSort, Options
@section Aquiring source and target drive
@c man .B Aquiring source and target drive:
@c man .PP