1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Why doesn't ffind find directory?

Discussion in 'Support' started by David Marcus, Mar 17, 2014.

  1. David Marcus

    Joined:
    Jun 4, 2008
    Messages:
    649
    Likes Received:
    1
    Would someone please explain why "ffind Files" below doesn't find anything?

    Code:
    C:\Junk>dir
    
    Volume in drive C is unlabeled      Serial number is 2af5:c418
    Directory of  C:\Junk\*
    
    3/14/2014   5:04p        <DIR>    Files
                     0 bytes in 0 files and 1 dir
       185,415,905,280 bytes free
    
    C:\Junk>ffind  Files
    
          0 files
    
    C:\Junk>ffind  File*
    C:\Junk\Files
    
          1 file
    
    C:\Junk>ffind  Files*
    C:\Junk\Files
    
          1 file
    
    C:\Junk>ver
    
    TCC  16.00.43 x64   Windows 7 [Version 6.1.7601]
    
    C:\Junk>
     
  2. vefatica

    Joined:
    May 20, 2008
    Messages:
    8,058
    Likes Received:
    30
    Because, with that syntax, FFIND looks for things **inside** the "Files" directory (and apparently, that directory is empty).
     
  3. Charles Dye

    Charles Dye Super Moderator
    Staff Member

    Joined:
    May 20, 2008
    Messages:
    3,352
    Likes Received:
    39
    Because there are no files in the directory you specify?

    A better question, I think, would be why FFILES does match the directory in the latter two. I suspect the answer is that, since there's a wildcard, FFILES 'knows' that you aren't specifying a search location.
     
  4. David Marcus

    Joined:
    Jun 4, 2008
    Messages:
    649
    Likes Received:
    1
    I don't see in the Help that you can specify a location. But, it seems to be acting like dir. "ffind /dc Files" does show the Files directory.
     

Share This Page