> > --- /usr/share/man/man5/pf.conf.5 Wed Mar 5 16:22:58 2014
> > +++ var1/man5/pf.conf.5 Thu Sep 3 16:19:21 2015
> > @@ -63,7 +63,7 @@ A method for detecting a host's operating system.
> > Some example rulesets.
> > .El
> > .Pp
> > -The current line can be extended over multiple lines using a backslash
> > +The current line can be extended over multiple lines using a
> > backslash-newline
> > .Pq Sq \e .
> > Comments can be put anywhere in the file using a hash mark
> > .Pq Sq # ,
> I would recommend:
> The current line can be extended over multiple lines using a backslash
> without trailing white space.
>
> I agree with later posts that nothing needs to be done to the parser. I
> have experienced the same error and wished it would give me the line
> number, but somehow I managed to find the mistake.
The sh man page, for instance, does not mention the problem with spaces
either:
A backslash in the input line causes the shell to prompt for further
input.
Yet millions of people have gotten by with reading and writing shell
scripts.
The same situation in for C.
So maybe we should wait until the exact same "improvement proposals"
arrive for the shell, the C language, and all the other programs that
behave in the same way?
Or the OP should admit they simply don't know unix. Yes, unix is
something you have to learn. There is not different from anything
else in life. I think it is pretty outrageous to suggest a few extra
words (term I use is "over-documentation") would have avoided this grief
in the first place. That is rewriting history; I am certain the OP
only is complaining after the fact.
This is not OpenBSD folk being mean. Very few people learn to ride a
bicicle without a scrape or two. Stop whining, and get back on the
bike.
The documentation is sufficient.
