On Sun, Mar 10, 2019 at 07:03:36PM -0500, Alfred Morgan wrote:
>    jmc wrote on? 2019-03-05 6:58:38:
>    > > How does this sound?
>    > > A specified option may be written inside curly brackets in order to
>    specify
>    > > a block of one or more specified options.
>    >?
>    > regarding your sentence - it's confusing. this is a tough one to
>    write,
>    > i think. from everything following that sentence to the end of that
>    > section, can everything take this {} notation?
>    Not everything. I found this difficult to explain because the manual
>    uses the word "option" as an argument to an "option" as well as the
>    main option. The manual does seem to distinguish the two terms by
>    referring to the option argument as a "specified option"
>    It would really help changing the sub-option name to something else,
>    like, "parameter", or "sub-option" but this would require an overhaul
>    that I was avoiding.

morning.

thanks for the feedback. i've tidied up your diff a bit. how does it
read?

i could do with feedback on two levels:

- does any developer want to ok alfred's proposed changes to the
  examples? i can;t commit this without one.

- does anyone want to nitpick the text regarding multiple options?

thanks,
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 06:54:47 -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 themselves be grouped 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" {

Reply via email to