Background
Imagine a user has these two aliases and one search directory item in FARR.
Alias1 (example of regex to get a single static result)
text: a
regex: ^a$
result: C:\folder\app.exe
Alias2 (example of regular expression aliases as search templates)
text: cdir
regex: ^(?:c|cd|cdi|cdir) (.+)$
result: dosearch +cdir $$1
Search Directory item
directory path: C:\cdir
optional modifier keywords: cdir
Problem case
The user types "c a" and want as result the list of files/folder in C:\cdir that contain "a".
But instead the result is "C:\folder\app.exe" . Because Alias1 is triggered by the new "a" search and since it is a regex alias it gets priority.
Collisions like that increase the more aliases of these two sorts one has. A pity since both sorts of aliases are useful.
Request for solution
Add a new virtual launch string named dosearch_noregex to FARR.
dosearch_noregex would start a new search but ignore all alias regex matches.
Imagine a user has these two aliases and one search directory item in FARR.
Alias1 (example of regex to get a single static result)
text: a
regex: ^a$
result: C:\folder\app.exe
Alias2 (example of regular expression aliases as search templates)
text: cdir
regex: ^(?:c|cd|cdi|cdir) (.+)$
result: dosearch +cdir $$1
Search Directory item
directory path: C:\cdir
optional modifier keywords: cdir
Problem case
The user types "c a" and want as result the list of files/folder in C:\cdir that contain "a".
But instead the result is "C:\folder\app.exe" . Because Alias1 is triggered by the new "a" search and since it is a regex alias it gets priority.
Collisions like that increase the more aliases of these two sorts one has. A pity since both sorts of aliases are useful.
Request for solution
Add a new virtual launch string named dosearch_noregex to FARR.
dosearch_noregex would start a new search but ignore all alias regex matches.











