Guidebook tweak - options parsing

This commit is contained in:
PatR
2019-02-11 16:30:46 -08:00
parent 4bb5560961
commit 1a8a774719
2 changed files with 21 additions and 5 deletions
+11 -4
View File
@@ -1,4 +1,4 @@
.\" $NHDT-Branch: NetHack-3.6.2-beta01 $:$NHDT-Revision: 1.292 $ $NHDT-Date: 1546984605 2019/01/08 21:56:45 $ .\" $NHDT-Branch: NetHack-3.6.2-beta01 $:$NHDT-Revision: 1.296 $ $NHDT-Date: 1549931433 2019/02/12 00:30:33 $
.\" .\"
.\" This is an excerpt from the 'roff' man page from the 'groff' package. .\" This is an excerpt from the 'roff' man page from the 'groff' package.
.\" NetHack's Guidebook.mn currently does *not* adhere to these guidelines. .\" NetHack's Guidebook.mn currently does *not* adhere to these guidelines.
@@ -2638,15 +2638,15 @@ Prefix a boolean option with \(lqno\(rq or \(oq!\(cq to turn it off.
For compound options, the option name and value are separated by a colon. For compound options, the option name and value are separated by a colon.
Some options are persistent, and apply only to new games. Some options are persistent, and apply only to new games.
You can specify multiple OPTIONS statements, and multiple options You can specify multiple OPTIONS statements, and multiple options
in a single OPTIONS statement. separated by commas in a single OPTIONS statement.
(Comma separated options are processed from right to left.)
.pg .pg
Example: Example:
.sd .sd
.ft CR .ft CR
OPTIONS=dogname:Fido OPTIONS=dogname:Fido
.\" '\(dq' == double quote; including a literal double quote here works .\" '\(dq' == double quote; including a literal double quote here works
.\" for formatting but confuses Emacs' nroff-mode into thinking .\" for formatting but confuses Emacs' nroff-mode
.\" that the \fP is part of a string rather than a font toggle
OPTIONS=!legacy,autopickup,pickup_types:$\(dq=/!?+ OPTIONS=!legacy,autopickup,pickup_types:$\(dq=/!?+
.ft .ft
.ed .ed
@@ -2802,6 +2802,13 @@ to that shell), or the pair of commands
.ED .ED
in \fIsh\fP, \fIksh\fP, or \fIbash\fP. in \fIsh\fP, \fIksh\fP, or \fIbash\fP.
.pg .pg
The NETHACKOPTIONS value is effectively the same as a single OPTIONS
statement in a configuration file.
The \(lqOPTIONS=\(rq prefix is implied and comma separated options are
processed from right to left.
Other types of configuration statements such as BIND or MSGTYPE are
not allowed.
.pg
Instead of a comma-separated list of options, Instead of a comma-separated list of options,
NETHACKOPTIONS can be set to the full name of a configuration file you NETHACKOPTIONS can be set to the full name of a configuration file you
want to use. want to use.
+10 -1
View File
@@ -2885,7 +2885,8 @@ Prefix a boolean option with `no' or `!' to turn it off.
For compound options, the option name and value are separated by a colon. For compound options, the option name and value are separated by a colon.
Some options are persistent, and apply only to new games. Some options are persistent, and apply only to new games.
You can specify multiple OPTIONS statements, and multiple options You can specify multiple OPTIONS statements, and multiple options
in a single OPTIONS statement. separated by commas in a single OPTIONS statement.
(Comma separated options are processed from right to left.)
%.pg %.pg
Example: Example:
@@ -3075,6 +3076,14 @@ to that shell), or the pair of commands
\nd in {\it sh}, {\it ksh}, or {\it bash}. \nd in {\it sh}, {\it ksh}, or {\it bash}.
%.pg
The NETHACKOPTIONS value is effectively the same as a single OPTIONS
statement in a configuration file.
The ``OPTIONS='' prefix is implied and comma separated options are
processed from right to left.
Other types of configuration statements such as BIND or MSGTYPE are
not allowed.
%.pg %.pg
Instead of a comma-separated list of options, Instead of a comma-separated list of options,
NETHACKOPTIONS can be set to the full name of a configuration file you NETHACKOPTIONS can be set to the full name of a configuration file you