On Mon, Mar 11, 2019 at 08:59:30AM -0700, Evan Silberman wrote:
>
>
> > On Mar 10, 2019, at 11:55 PM, Jason McIntyre <[email protected]> wrote:
> >
> > +Directives which take multiple
> > +.Ar option
> > +values may themselves be grouped in curly brackets.
>
> I think this implies that the directives (which take multiple option values)
> may be grouped in curly brackets rather than implying the options and their
> values may be grouped in curly brackets as a parameter to the root directive.
> I would try something like:
>
you're right, it's ambiguous. but...
> For some options, the possible values are another set of options. In these
> cases, the main option can be repeated, setting a different suboption each
> time, or the main option may be followed by a block enclosed by curly braces,
> within which each suboption may be set without repeating the name of the main
> option.
>
> I???m not super happy with this paragraph, which gives up brevity for
> precision, but I do think it???s more precise.
>
i don;t really want to go down the road of talking about suboptions!
also the text is super long. i've tweaked my text below. if we can't get
it clear and concise, it might just be easier to give an example.
jmc
Index: httpd.conf.5
===================================================================
RCS file: /cvs/src/usr.sbin/httpd/httpd.conf.5,v
retrieving revision 1.103
diff -u -r1.103 httpd.conf.5
--- httpd.conf.5 19 Feb 2019 11:37:26 -0000 1.103
+++ httpd.conf.5 11 Mar 2019 19:05:57 -0000
@@ -155,7 +155,10 @@
.Xr patterns 7 .
.El
.Pp
-Followed by a block of options that is enclosed in curly brackets:
+It is followed by a block of directives and values, enclosed in curly brackets.
+Directives which take multiple
+.Ar option
+values may also group these options in curly brackets.
.Bl -tag -width Ds
.It Ic alias Ar name
Specify an additional alias
@@ -714,9 +717,14 @@
.Bd -literal -offset indent
server "www.example.com" {
alias "example.com"
- listen on * port 80
- listen on * tls port 443
+ listen on * port http
+ listen on * tls port https
root "/htdocs/www.example.com"
+
+ tls {
+ key "/etc/ssl/private/example.com.key
+ certificate "/etc/ssl/example.com.fullchain.pem"
+ }
}
server "www.a.example.com" {
