Search for colon-containing keys broken

[Ldp]

Searching for colon-containing keys was broken in the past few days. Searching for one, for instance "a:b"=1 brings up a popup:

Unexpected token: <number>

[Ldp]

Also broken:

nodes:100-2000

[avarab@…]

Also broken: Tokens separated by =:

ref=1234

Adding this as a release blocker.

[Gubaer]

Looks like a regression, possibly introduced in r2973?

[jttt]

Yes, it was introduced in r2973. I'll fix it.

[jttt]

(In [2993]) Fix #4528 Search for colon-containing keys broken

[avarab@…]

Replying to jttt:

(In [2993]) Fix #4528 Search for colon-containing keys broken

This fix broke searches like:

type:node

and:

^foo$:bar$

When using regex search

[jttt]

(In [2995]) Fix #4528: Search for colon-containing keys broken

[jttt]

Btw ^foo$:^bar$ is no longer necessary, foo=bar does the same thing

[avarab@…]

Replying to jttt:

Btw ^foo$:^bar$ is no longer necessary, foo=bar does the same thing

I just added it as a testcase showing that regex search was also broken, but thanks.