pdir /(fq) not working

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
#1
TCMD 10.00.46

It looks like the new /(fq) option on pdir is not working. pdir /(f) works, but if I add the q, I get no output from the pdir command.

[C:\temp\temp]dir

Volume in drive C is VistaOS Serial number is 1a79:1110
Directory of C:\temp\temp\*

[C:\temp\temp]dir

Volume in drive C is VistaOS Serial number is 1a79:1110
Directory of C:\temp\temp\*

2/02/2009 16:03 0 abc.txt
2/02/2009 16:03 0 def ghi.txt
0 bytes in 2 files and 2 dirs
8,117,493,760 bytes free

[C:\temp\temp]pdir /(f) *
abc.txt
def ghi.txt

[C:\temp\temp]pdir /(fq) *

[C:\temp\temp]
 
#2
I get the same thing.
I also noticed an interesting thing testing /(fN) vs. /(fn). I had a long
filename, but it had no short filename. The long filename was created with
mklnk. It looks like Windows/TCC does not auto-create a short filename
during the link process. I'm not complaining about that, but it did make me
wonder and investigate for a few minutes while I wondered whether pdir had a
problem.

On Sun, Feb 1, 2009 at 7:12 PM, Stephen Worthington
<>wrote:


> TCMD 10.00.46
>
> It looks like the new /(fq) option on pdir is not working. pdir /(f)
> works, but if I add the q, I get no output from the pdir command.
>
> [C:\temp\temp]dir
>
> Volume in drive C is VistaOS Serial number is 1a79:1110
> Directory of C:\temp\temp\*
>
> 2/02/2009 16:03 <DIR> .
> 2/02/2009 16:03 <DIR> ..
> 2/02/2009 16:03 0 abc.txt
> 2/02/2009 16:03 0 def ghi.txt
> 0 bytes in 2 files and 2 dirs
> 8,117,493,760 bytes free
>
> [C:\temp\temp]pdir /(f) *
> abc.txt
> def ghi.txt
>
> [C:\temp\temp]pdir /(fq) *
>
> [C:\temp\temp]
>
>
>
>
>


--
Jim Cook
2009 Saturdays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Sunday.
 
#4
Since "dir /x" didn't show anything, nor did my own timedir when looking at
the Find structure, I suspected as much.
Mostly , I hoped to put some more information out there in case somebody
else got confused also. Thankfully both @LINKS and my program showed 2, and
that was when I became pretty certain it wasn't a flaw in PDIR.

On Mon, Feb 2, 2009 at 10:40 AM, rconn <> wrote:


> ---Quote (Originally by Jim Cook)---
> I get the same thing.
> I also noticed an interesting thing testing /(fN) vs. /(fn). I had a long
> filename, but it had no short filename. The long filename was created with
> mklnk. It looks like Windows/TCC does not auto-create a short filename
> during the link process.
> ---End Quote---
>
> That's Windows, not TCC.
>
>
>
>
>


--
Jim Cook
2009 Saturdays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Sunday.
 
#6
On Mon, 02 Feb 2009 20:46:27 -0600, you wrote:


>---Quote---
>> TCMD 10.00.46
>>
>> It looks like the new /(fq) option on pdir is not working. pdir /(f)
>> works, but if I add the q, I get no output from the pdir command.
>>
>> [C:\temp\temp]pdir /(fq) *
>---End Quote---
>The 'q' option requires you to also specify the P, p, N, or n option.
>
>Rex Conn
>JP Software
Ok, so it is just a problem with the documentation then. I have never
used PDIR /(f) before, so I had no idea from the help file that I
needed one of the other options too. PDIR /(f) does work and seems to
be the same as PDIR /(fn), so I think it would be best if PDIR /(fq)
did the same as PDIR /(fnq).

BTW Thanks a lot for the q option. It makes it much easier to create
ad hoc batch files to do things to a list of files. I have frequently
found myself using my text editor to add the quotes manually.