Directory wildcards not working with ffind

Mar 20, 2009
39
1
I have tried using directory wildcards and the seemed to work ok with dir or pdir but the same argument with ffind does not work.
example:

C:\Howard\working>pdir/(f) "c:\Program Files\JP*\"*\*.exe
ide.exe
ShrAlias.exe
tcc.exe
tcmd.exe
updater.exe

C:\Howard\working>ffind "c:\Program Files\JP*\"*\*.exe

0 files

This also fails with just the single wildcard \*\
 
Mar 20, 2009
39
1
FFIND is one of the few commands that does not implement directory wildcards because it's not meaningful. (Your example does the same thing as DIR or PDIR, only not as well.)

The documentation for directory wildcards is very limited. There is more information in the what's new area than in the File Selection/wildcards and regular expression section of help. This directory wildcards would be useful if /t option was used with ffind.

After thinking about it using /s with directory wildcards seems to be confusing and I think I got TCC to crash in some cases before I realized the conflict.

Additional documentation of directory wildcards would be useful.
 

rconn

Administrator
Staff member
May 14, 2008
12,344
149
The documentation for directory wildcards is very limited. There is more information in the what's new area than in the File Selection/wildcards and regular expression section of help. This directory wildcards would be useful if /t option was used with ffind.

Windows goes to great lengths to prevent directory wildcards from working. It took a couple thousand lines of code and additional custom code for every file-handling command or function to support it, so (like CLIP:) it only gets added where it's most sensible / useful.

FFIND is particularly problematic, but I'll see if something can be done to support it in the case of text searching.

After thinking about it using /s with directory wildcards seems to be confusing and I think I got TCC to crash in some cases before I realized the conflict.

As the help says, combining /S with directory wildcards is a sure path to destruction. I doubt you'll crash in TCC code, but you can certainly easily get into near-infinite loops and blow your stack, or crash inside Windows APIs that don't expect to be called recursively.
 
Similar threads
Thread starter Title Forum Replies Date
D erase with directory wildcards Support 16
fishman@panix.com HELP!! I just updated to Version 28 and as usual I cannot make extended directory search work. Support 2
D How to use multi-line DO to loop through first level directory names Support 5
D ParentDirectory does not update directory history Support 6
samintz CDD to non-existent directory hangs Support 2
gworley rd (Remove Directory) gives interesting error: Support 2
D Directory History Window with wildcard search Support 3
D How to? Skip removing directory (RMDIR) without error message Support 2
gentzel Directory stack empty when running TCEXIT? Support 9
vefatica Disable extended directory searches (completely)? Support 8
M WAD "Pictures" directory is empty in TCC but not in CMD or Explorer Support 4
G Local Directory Corruption Support 11
Jay Sage Directory Alias Access to FTP Servers Support 2
Joe Caverly DIRectory Colorization in v25 Help File Support 0
K copy changing destination current directory Support 1
thorntonpg option /u not working The directory name is invalid Support 5
J built in file explorer - how do i go back "up" the directory? Support 2
vefatica Extended directory searches? Support 6
Joe Caverly Using a Directory Alias with @iniwrite fails Support 14
A Installer /extract: extracts into current directory if target not exists Support 12
Charles Dye Ctrl-Shift-Up doesn't update directory history Support 1
G Extended directory search not working Support 4
CWBillow Editing in the root directory of windows 10 Support 6
D Directory stack empty Support 1
J directory or folder to start in Support 2
M How to unlock a directory Support 1
Alpengreis Fixed TCMD FileExplorer Start-Directory problem Support 4
R V19 - At startup, TCC save directory in the directory history list Support 2
C Touch command — I Need to touch matching files in another directory. Support 5
nickles Move takecommand.18.0.key location to installation directory Support 4
fishman@panix.com Extended Directory Searches are not working for me in CDD Support 9
vefatica TCMD's current directory? Support 4
J How to set working directory Support 10
nickles How to? Follow a JUNCTION type directory link Support 9
Steve Pitts WAD Strange output from DEL of a non-existent directory Support 7
I tab completion with directory commands Support 7
vefatica Start-up directory for new tabs? Support 7
cgunhouse Problem with CALL and Directory Aliases in V17 Support 9
vefatica FFIND /S, find directory with specified name? Support 7
David Wilbanks How to make new tab open in same directory as previous tab? Support 4
H WAD Wild Card in Directory @shfolder[25] acting differently Support 3
M How to? List path getting short file and directory names... Support 10
A How to? Can't change directory ("cd") into system hidden files Support 13
mfarah How to? So I want a custom directory for the plugins... Support 16
D Why doesn't ffind find directory? Support 3
T dir /h error in empty directory Support 22
S directory history locks up TCC Support 3
B Why Does @GETDIR Repeat Selected Directory Name In Returned Value Support 7
ed neff How to? exit TCC/Take Command to a new directory Support 10
Jake Default directory Support 3

Similar threads