My observation on result still stands. There is no way to specify no way to say
"everything below here but not here" If it were a regular expression it would be here:[.]+ which would match here:one here:two but not here It just seems to me that the colon before the wildcard should indicate a single new segment and we don't care what it is. This is the way it works for all the other instances of the wild card. so X:*:Z means matches the regular expression X:[^:]+:Z in english: X, colon, anything but colon, colon, Z The colon is critical in the pattern match. But when the wildcard is on the end the colon is ignored X:* in english is: X, anything I think it should be X, colon, anything. I think the colon is important. But I suppose it is too late to change the way the wild card works now. Claude On Fri, Jan 26, 2018 at 3:03 PM, Brian Demers <brian.dem...@gmail.com> wrote: > Grab the referenced PR and try to build it. > > Let me know if that doesn't work, > -Brian > > On Fri, Jan 26, 2018 at 2:22 AM, Claude Warren <cla...@xenei.com> wrote: > > > Hmmmmm.... I must have something off in my code. as P2 does not imply P1 > in > > my test code. > > > > So the end result is that there is no way to say > > > > "everything below here but not here" > > > > If it were a regular expression it would be here:[.]+ > > > > which would match > > > > here:one > > here:two > > > > but not > > > > here > > > > Claude > > > > > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
