>
>
>> Or just "newline-sensitive matching" ... does "full" add anything?
>>
>
And since I'm nit-picking anyway - the word "sensitive" does nothing for
me. Simply "newline-matching" would be sufficient, ideally. i.e., Do ".
[^]" and "^$" match the newline character, or not.
[w] anchor newline-m
On Thu, Jun 5, 2014 at 8:00 PM, Tom Lane wrote:
> David G Johnston writes:
> > I simplified ". and bracket expressions" to "wildcard" and "^ and $" to
> > "anchors" though did make use of ^ and $individual quite a bit. I did
> not
> > formally define these terms in the body either.
>
> Did you
David G Johnston writes:
> I simplified ". and bracket expressions" to "wildcard" and "^ and $" to
> "anchors" though did make use of ^ and $individual quite a bit. I did not
> formally define these terms in the body either.
Did you mean to attach a proposed doc patch here, or are you just
armwa
The current documentation for "n" and "w" are as follows:
[s] If partial newline-sensitive matching is specified, this affects . and
bracket expressions as with newline-sensitive matching, but not ^ and $.
[w] If inverse partial newline-sensitive matching is specified, this affects
^ and $ as wit
