(Switching to evergreen-users, devadmin to bcc.)
Do you have precedent, from some other application, for " " searching for \s+? Such things weigh heavily, even in the absence of a patch.
From: Alan Carwile
Sent: Friday, November 18, 2011
12:33
To: Martin Dorey; Eric Wedel; @Dev Admin
Subject: RE: A little edit for dev
wiki - boogle link
From: Martin Dorey
Sent: Friday, November 18, 2011
12:15 PM
To: Alan
Carwile; Eric Wedel;
@Dev Admin
Subject: RE: A little edit for dev
wiki - boogle link
...
> I thought it should have worked and matched, since a newline is whitespace.
If you asked it to search for correct\s+and\s+up\s+to\s+date then you'd have a case, although evergre...@googlegroups.com would be a better place to report it. Patches assuredly welcome. Such searches work within a file, but not with Find in Files.
Splitting sentences across lines is asking for such problems, and it makes the line-based revision history tools less useful.
[adc: ] I’ll just search for stuff at the beginning of the paragraph or the end where there’s less likely to be a newline intervening. I definitely won’t type \s everywhere as a rule.
From: Alan Carwile
Sent: Friday, November 18, 2011
12:03
To: Eric
Wedel; Martin Dorey; @Dev Admin
Subject: RE: A little edit for dev
wiki - boogle link
...
Side note: I searched in evergreen for this in the docs repo:
content being correct and up to date
but got no matches, probably because the text breaks over a newline in the source
but don't expect perfection and do not rely on any of the content being correct and up to
date without checking with someone in development first.
I thought it should have worked and matched, since a newline is whitespace.
Alan
"Google"? :-)
> ________________________________
>
> From: Alan Carwile
> Sent: Friday, November 18, 2011 12:33
> To: Martin Dorey; Eric Wedel; @Dev Admin
> Subject: RE: A little edit for dev wiki - boogle link
>
>
>
> From: Martin Dorey
> Sent: Friday, November 18, 2011 12:15 PM
> To: Alan Carwile; Eric Wedel; @Dev Admin
> Subject: RE: A little edit for dev wiki - boogle link
>
>
>
> ...
>
>
>
>> I thought it should have worked and matched, since a newline is
>> whitespace.
>
>
>
> If you asked it to search for correct\s+and\s+up\s+to\s+date then you'd have
> a case, although evergre...@googlegroups.com would be a better place to
> report it. Patches assuredly welcome. Such searches work within a file,
> but not with Find in Files.
how come? i thought Find/Replace was the only awkward case. (given its
line-based preview.)
> Splitting sentences across lines is asking for such problems, and it makes
> the line-based revision history tools less useful.
>
>
>
> [adc: ] I’ll just search for stuff at the beginning of the paragraph or the
> end where there’s less likely to be a newline intervening. I definitely
> won’t type \s everywhere as a rule.
>
>
>
> ________________________________
>
> From: Alan Carwile
> Sent: Friday, November 18, 2011 12:03
> To: Eric Wedel; Martin Dorey; @Dev Admin
> Subject: RE: A little edit for dev wiki - boogle link
>
>
>
> ...
>
>
>
> Side note: I searched in evergreen for this in the docs repo:
>
> content being correct and up to date
>
> but got no matches, probably because the text breaks over a newline in the
> source
>
> but don't expect perfection and do not rely on any of the content being
> correct and up to
>
> date without checking with someone in development first.
>
> I thought it should have worked and matched, since a newline is whitespace.
>
>
>
> Alan
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "evergreen-users" group.
> To post to this group, send email to evergre...@googlegroups.com.
> To unsubscribe from this group, send email to
> evergreen-use...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/evergreen-users?hl=en.
>
--
Elliott Hughes - http://www.jessies.org/~enh/