get-childitem bug?

I seems to me that the -include option doesn't work for a file extension. In
my output ( below) get-childitem finds the files in the current directory.
When I apply the -include foo* for a file NAME, it finds the files with the
pattern/wildcard. When I apply the -include *.txt no files are found ( see
last line below). Is it just me? Thanks for input or confirmation.

-------------------------------------------------------------------------------------
PS C:\Temp\foodir> get-childitem

Directory: Microsoft.PowerShell.Core\FileSystem::C:\Temp\foodir

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 2/29/2008 9:59 AM 46 foo.txt
-a--- 2/29/2008 10:00 AM 21 foo2
-a--- 2/29/2008 9:57 AM 9 foo2.txt


PS C:\Temp\foodir> get-childitem .
Directory: Microsoft.PowerShell.Core\FileSystem::C:\Temp\foodir

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 2/29/2008 9:59 AM 46 foo.txt
-a--- 2/29/2008 10:00 AM 21 foo2
-a--- 2/29/2008 9:57 AM 9 foo2.txt

PS C:\Temp\foodir> get-childitem . -include foo*
Directory: Microsoft.PowerShell.Core\FileSystem::C:\Temp\foodir

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 2/29/2008 9:59 AM 46 foo.txt
-a--- 2/29/2008 10:00 AM 21 foo2
-a--- 2/29/2008 9:57 AM 9 foo2.txt


*** Next line returns NO OUTPUT ****
PS C:\Temp\foodir> get-childitem . -include *.txt
PS C:\Temp\foodir>

Check te help for get-childitem include parameter:

-include <string[]>
Retrieves only the specified items. The value of this parameter qualifies
the Path parameter. Enter a path element or pattern, such
as "*.txt". Wildcards are permitted.

The Include parameter is effective only when the command includes the
Recurse parameter or the path leads to the contents of a dire
ctory, such as C:\Windows\*, where the wildcard character specifies the
contents of the C:\Windows directory.


That said, this should fix the problem:

get-childitem .\* -include *.txt


-----
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com

Shay, thanks. The qualified -path does solve the issue. I did read the
help originally, and I used Example 2 - (( C:\PS>get-childitem . -Include
*.txt -Recurse ))
which does not follow the Qualified -path requirement.
It seems inconsistent if one -include pattern works, and another -include
pattern doesn't work, when in both cases, the -path is not fully qualified.
Maybe better in 2.0...

I appreciate your help.


"Shay Levi" wrote: