PDIR woes

alias dirl=pdir /a:j /(fpn" ==^> "@junction
[*])

dirl ..App* .KLS.pete*
C:\..Apps ==> Volume{14a1b9f1-89e6-11de-9861-001e8cc44bce}\
C:\.KLS.peter ==>

alias dirl=pdir /a:j /(fpn" ==^> "@symlink
[*])

dirl ..App* .KLS.pete*
C:\..Apps ==>
C:\.KLS.peter ==> \\kls\peter

So I tried

alias dirl-js=pdir /a:j /(fpn" ==^> "@junction
[*]@symlink
[*])

dirl-js ..App* .KLS.pete*
C:\..Apps ==> Volume{14a1b9f1-89e6-11de-9861-001e8cc44bce}\@symlink
[*]
C:\.KLS.peter ==> @symlink
[*]alias dirl-sj=pdir /a:j /(fpn" ==^> "@symlink
[*]@junction
[*])
dirl-sj ..App* .KLS.pete*
C:\..Apps ==> @junction
[*]
C:\.KLS.peter ==> \\kls\peter@junction
[*]

Why don't these work? And why does the following (note the space before @junction[] which is also actually there in the output (but swallowed by the posting mechanism) ... ugly!)?

alias dirl-sj=pdir /a:j /(fpn" ==^> "@symlink
[*] @junction
[*])
dirl-sj ..App* .KLS.pete*
C:\..Apps ==> Volume{14a1b9f1-89e6-11de-9861-001e8cc44bce}\
C:\.KLS.peter ==> \\kls\peter


And not entirely related, but I discovered it while I was messing around with the above:

dir c:\]Desk*
Volume in drive C is System Serial number is e2af:ec3b
Directory of C:\]Desk*

2009-08-15 21:51 <symlinkd> ]Desktop [C:\Users\peter\Desktop]</symlinkd>
0 bytes in 0 files and 1 dir
846,883,254,272 bytes free<symlinkd>

(Yes, I have a symlink called C:\]Desktop". Perverse perhaps, but completely legal).

echo %@symlink[c:\]Desktop]
Desktop]

Is there a way around this? It would not work in the pdir context anyway, but I tried replacing the ] with ? but @junction/@symlink don't take wildcards.

(TCC 10.00.76 Windows 7 [Version 6.1.7600])</symlinkd>
 
Similar threads
Thread starter Title Forum Replies Date
D PDIR question Support 0
Phileosophos PDIR to list filenames without extensions? Support 2
vefatica PDIR and streams Support 1
vefatica PDIR with fixed-width unqualified filename? Support 2
W pdir returns diff results between tcc and tcmd - one is an error msg Support 5
thedave pdir /s Support 2
Emilio III pdir /f switch Support 1
D pdir ignores pm Support 2
WadeHatler pdir broken in 19.1 for directories with spaces Support 1
M WAD PDir not working correctly... Support 5
vefatica WAD Nested variable expansion in PDIR's @function[*]? Support 13
mfarah More on pdir's options: /(fq) Support 5
mfarah How to? Getting pdir to display relative paths. Support 2
S PDIR and @LABEL questions Support 4
M How to? PDir on multiple wildcard patterns... Support 2
A pdir function usage Support 3
T How to? dir/pdir - 2nd level down only Support 7
JohnQSmith PDIR and descriptions Support 21
G WAD PDIR @IF bug, @WORD bug Support 8
S WAD PDIR: files with percent sign % in name cause not listing other files in directory Support 9
S WAD PDIR ignores exclusion ranges Support 1
M PDir format question... Support 3
M How to? "PDir" not working the way the I _thought _ the documentation said it does… Support 8
S WAD /Sn mishandled in DIR and PDIR, possibly elsewhere Support 15
S Fixed GPF in PDIR Support 3
S PDIR issue Support 1
M PDir causing Take Command/TCC to crash... Support 6
M A "PDir" issue... Support 16
M A simple question related to the "dir" (and "pdir") commands... Support 5
J pdir /b1 issue Support 20
M Missing PDir option... Support 5
J Maybe Not So Hard Pdir Question Support 1
S PDIR fails in 12.10.55 Support 3
J V12 PDIR failure Support 1
S PDIR command causes GPF Support 5
D pdir inconsistency Support 4
S PDIR has trouble processing filenames with embedded percent sign Support 3
gschizas pdir crashes horribly in one specific folder Support 5
S PDIR question Support 2
S pdir /(fq) not working Support 5
R Colored directory listing bug with pdir. Support 1
nickles Bias in PDIR Support 5
F pdir problem Support 3
D can PDIR list full filepaths of docs in a nested folder? Support 13
K_Meinhard Everything installation woes again Support 0
vefatica Win10 woes. Support 4
vefatica WAD More SET /A woes Support 4
vefatica Build 20 installer woes Support 14
vefatica Installer woes Support 3
nikbackm WAD More Windows 10 woes Support 8

Similar threads