Hi Jason, That's what I wasn't sure about - haven't seen many "that" used in that way ;^)
Thanks for the explanation. Raf On Tue, Aug 29, 2017 at 09:35:25PM BST, Jason McIntyre wrote: > On Tue, Aug 29, 2017 at 09:22:30PM +0100, Raf Czlonka wrote: > > Hi all, > > > > Not entirely sure what the author had in mind but the current > > sentence, as it is, doesn't seem right somehow. > > > > The below is my best guess. > > > > Cheers, > > > > Raf > > > > hi. > > what's there is fine. it is a common text blurb in many similar pages. > i'm not sure how to explain it grammatically, but in this context "that" > is just a way of pointing back to "macros". > > so it would probably be nicer to say: > > Macros can be defined, which will later be expanded in context. > > relative pronouns...? "that" is a sloppy catch all, but it is valid. > > jmc > > > Index: usr.sbin/ldapd/ldapd.conf.5 > > =================================================================== > > RCS file: /cvs/src/usr.sbin/ldapd/ldapd.conf.5,v > > retrieving revision 1.22 > > diff -u -p -r1.22 ldapd.conf.5 > > --- usr.sbin/ldapd/ldapd.conf.5 17 Oct 2016 14:03:17 -0000 1.22 > > +++ usr.sbin/ldapd/ldapd.conf.5 29 Aug 2017 20:18:33 -0000 > > @@ -41,7 +41,7 @@ must be quoted. > > Arguments containing whitespace should be surrounded by double quotes > > .Pq \&" . > > .Pp > > -Macros can be defined that will later be expanded in context. > > +Macros can be defined and will later be expanded in context. > > Macro names must start with a letter, digit, or underscore, > > and may contain any of those characters. > > Macro names may not be reserved words (for example > > >
