FFIND /S, find directory with specified name?

[vefatica]

How can I get FFIND /S to find a directory with a specified name (and only directories with that specified name)? Below, how do I find "g:\tc17" only?

v:\> ffind /s /a:d g:\tc17
G:\tc17\plugins
G:\tc17\Styles

  2 files

v:\> ffind /s /a:d g:\tc17*
G:\tc17
G:\tc177

  2 files

 

[Charles Dye]

How about FFIND /S /A:D G:\TC1[7]

 

[vefatica]

How about FFIND /S /A:D G:\TC1[7]

Yeah, that works but it's quite a kludge to handle the simplest case in which I know exactly the name of what I'm looking for.

 

[Charles Dye]

You can also slap the brackets on the end: TC17[]

 

[vefatica]

You can also slap the brackets on the end: TC17[]

Same comment.

 

[Charles Dye]

I can't claim elegance. But if you want to specify a directory name to search for -- as opposed to a directory name to search in -- I think you must use a wildcard. And if you want a wildspec which can only match one specific filename, then the square brackets it is.

 

[mikea]

I thought my old standby — using “.” by itself at the end of a filename or directory name — would do the trick. As in: ffind /s /a:d c:\tc17.

Nope. But this did. Go figure:

ffind /s /a:d c:\tc17.*

I’d created c:\tc17 and c:\tc177. The command returned only c:\tc17 and not c:\tc177.

 

[rconn]

How can I get FFIND /S to find a directory with a specified name (and only directories with that specified name)? Below, how do I find "g:\tc17" only?

If you want to search for files (and not their contents), then DIR or PDIR will be faster than FFIND.