X-Git-Url: http://git.tuebingen.mpg.de/?a=blobdiff_plain;f=lopsub-suite.5.m4;h=1992b6ed80f57e0ec01ac5084470bfa1c11daa8e;hb=HEAD;hp=ff81198e1e184e2e294c221cfcb3044580b4e67e;hpb=816fbbbd5df22d732ab649fa9e264b7b6a27227a;p=lopsub.git

diff --git a/lopsub-suite.5.m4 b/lopsub-suite.5.m4
index ff81198..cd607a5 100644
--- a/lopsub-suite.5.m4
+++ b/lopsub-suite.5.m4
@@ -64,7 +64,7 @@ See the section on command directives below.
 
 Supercommands and subcommands share the same set of possible command
 directives. They differ mainly in the way the documentation is
-formated. There can only be one supercommand but arbitrary many
+formatted. There can only be one supercommand but arbitrary many
 subcommands. For example, the supercommand could be the name of
 the application, and the subcommands could be "load", "save" "info"
 and "quit". The subcommand would be passed as the first non-option
@@ -144,9 +144,7 @@ way with
 and
 .BR [/conclusion] .
 Both texts will become part of the manual page, but are not not part
-of the short or long help. Like for the
-.B section
-directive, arbitrary roff source may be included here.
+of the short or long help.
 .TP
 .B aux_info_prefix
 This text is shown at the bottom of each command before the value of the
@@ -305,6 +303,12 @@ only given in the config file. The recommended way to deal with
 this situation is to parse command line and config file separately,
 then merge the two parse results and check in the application if the
 option is given in the merged parse result.
+
+There is another disadvantage of this flag: if the parser fails due
+to a missing option that was declared required, it is not possible to
+detect if other options were given. For example, if the suite defines
+the --help option, and the application is executed with this option
+only, the parser will still return a parse error.
 .B
 .IP ignored
 This flag indicates that the current option is in fact not a real option.