possible regex search alias bug

[Nod5]

Hi, I have a conflict with two aliases. To reproduce, make these two regex aliases:

Code

^(.*)\s\s$ 

and

Code

^aa((?: .*|))$

If I type "aa[space]" in FARR the first alias is mistakenly triggered. Is that a bug?

[mouser]

strange.. can i ask if you haven't given a NAME to the first alias that might cause it being triggered?

[Nod5]

No this reproduces whatever name I set for it.

More testing: if I open the "edit group alias" window for the first alias and enter "aa " in the test box it (correctly) says "no match" in red text. But I enter "aa " (without quotation marks) in the regular FARR inputbox the first alias runs. Weird!

I tried tweaking the second alias into the below, but the problem is still there.

Code

^aa( .*)$

edit:
hm, if I use this the problem also occurs

Code

^aa(|.+)$

but if I use this there is no problem

Code

^aa(| .+)$

A drawback is that with this last regex the alias first runs on "aa", then a regular FARR search is shown on "aa " and then the alias runs again on "aa test". I use this alias to on "aa" list all files in a folder and on "aa test" list all files in that folder matching the phrase test. Anyway, I don't understand why the problem appears in all but the last version of the regex.

[mouser]

I cannot reproduce it.. i suspect the problem is caused by interaction with another alias.

Try this:

type "bb "

if this does not mistakenly trigger your first alias, then you know the problem is not with your first alias, but with some other interaction with ANOTHER alias triggering on the aa.

[Nod5]

"bb " does nothing. But what makes me think there is some issue with FARR here is that if I change the second alias from

Code

^aa(|.+)$

to

Code

^testing(|.+)$

I still have the problem i.e. "testing " triggers the first alias.

I have checked my list of aliases and found no third alias triggering on "aa" (nor on "testing"). Could this be related to the fact that the aa-alias is designed to trigger both on "aa" and on "aa whatever"?

Anyway, since

Code

^aa(| .+)$

works good enough I'm by now just curious why there is a difference.

edit: Let me add that  the two aliases are used to launch these actions

Code

^aa(|.+)$
aa | dosearch C:\test\ $$1

Code

^(.*)\s\s$
dolaunch copyclip $$1 ;;; C:\ev2.exe

where ev2.exe is my workaround autohotkey script that passes a search to everything

[Nod5]

Aha! The problem is a space in the dosearch command string. If I change

Code

aa | dosearch C:\test\ $$1

into

Code

aa | dosearch C:\test\$$1

the problem is solved.

[mouser]

I'm still a bit confused but it sounds like you are saying that what happened was the proper alias was triggered and then as it's action it replaced the search with text that immediately matched the other alias.

[skajfes]

The problem is with the aa alias.
You are capturing the space with the search string.
So when you type in

Code

aa[space]

FARR captures the space as $$1. Then in turn, you pass $$1 along to the result and have

Code

dosearch C:\test\[space][space]

that triggers the other alias that matches on \s\s.

I think it is good practice not to capture the space before the parameters. There is less chance of bugs like this.

[Nod5]

mouser & skajfes: you are right, thank you for the explanation.  

skajfes: good practice in general - agreed! But in this particular case I wanted the alias to trigger first on "aa" (show all files in a folder) and on "aa somephrase" (show files in the folder matching "somephrase") *and* not switch back to a regular FARR search inbetween that. For that I needed the first space included in the match pattern.

[skajfes]

If I understand you correctly you can write a regex like this with same effect:

Code

^aa\s?(.*)$

[Nod5]

Yes, you're right, thanks! But why didn't I think of that?    

[skajfes]

No problem. I use regex fairly often, so this is a simple problem for me

Btw, thanks for the donation