bug: launch history bypass search directory file restrictions?

[Nod5]

Bug replicated with these settings:

ALIAS:
^b (\w.*)[^\+]$
C:\aaa $$1 | dosearch +aaa $$1

SEARCH DIRECTORY:
path: C:\aaa
restrictions: -txt;url;jpg
modifier keyword: aaa

Given that then entering "b test" in FARR should match C:\aaa\test.png but not C:\aaa\test.txt . But if the user has previously launched C:\aaa\test.txt then FARR seems to ignore the set restriction and displays C:\aaa\phrase.txt among the alias matches. FARR does not include other matching .txt files (like  C:\aaa\test2.txt ) until such other files also have been launched by FARR once.

(background: the last part of the regex -- [^\+]$ -- is there to disable this alias by adding "+" to the end of the search phrase and then immediately let another alias -- ^b (\w.*)\+$  -- search the same folder but without the restrictions, using another search directory modifier. If I get this problem sorted out then that will be a very handy way to have an alias toggle between limited/full search within some folders)

[skajfes]

You could always restrict file types in the alias instead of the search folder definition. The problem, as I see it, is that previously launched .txt file is added to launch history which is then evaluated in later searches. But then it is filtered only by entered search string (and not by search folder definition) and is therefore not excluded from the results as it should be.

Alias:
^b (\w.*)[^\+]$
C:\aaa $$1 | dosearch +aaa -.txt $$1

Search directory:
path: C:\aaa
restrictions: url;jpg
modifier keyword: aaa

[Nod5]

my alias doesn't work at all when I add "-.txt".
edit: I accidentally unticked the alias box.  Works now. In the alias the file restrictions need to be individual, like so:
C:\aaa $$1 | dosearch +aaa -.txt -.jpg -.url $$1

A problem: the restriction excludes any file containing ".txt" in extension OR name. So both "file.txt.pdf" and "file.txt" are excluded. To avoid that we'd need some way to specify the restriction. Compare: in regexp $ marks the end of the string so ".txt$" would do the trick there.

[skajfes]

A problem: the restriction excludes any file containing ".txt" in extension OR name. So both "file.txt.pdf" and "file.txt" are excluded. To avoid that we'd need some way to specify the restriction. Compare: in regexp $ marks the end of the string so ".txt$" would do the trick there.

-Nod5 (August 22, 2009, 08:13 AM)

Regex support in the search string would solve this easily. Though, I am not sure if it is really that needed.

[Nod5]

Right, I have no need for it ATM so I shouldn't call it a problem really. The aliases works as I hoped for now so all is well.