Jump to number fails about zlocation HOT 3 CLOSED

Oh very interesting! Sorry for not looking at it for 3 years - it somehow slipped out of my attention.

from zlocation.

I'm not 100% on what the issue is here:

• If the expected result of the top example is to end up in C:\temp\7, then I think ZLocation did the right thing: C:\temp\7 isn't a known location at that point (though its parent and child directories are), so ZLocation wouldn't jump to it. The ability to move to unknown directories added since this was opened means ZLocation would now move to C:\temp\7 now, as it'd be treated as a direct reference to the child directory 7.

• If the expected result is to end up C:\temp\7\test, then that's because the last step of Test-FuzzyMatch requires the query (7) to be part of the leaf of the path (test). Whether that's right could be debated, but ZLocation's functioned that way at least as long as there's been a separate search module (812596d#diff-93df13f76ff52d17e115d75e3c549004R44-R45)

$search = ipmo .\ZLocation\ZLocation.Search.psm1 -PassThru
& $search { Test-Fuzzymatch 'C:\temp\7\test' 7 } #False
& $search { Test-Fuzzymatch 'C:\temp\foo\test' foo } #False

from zlocation.

@theaquamarine feel free to close, this seems to be super old anyway

from zlocation.