cd =

Jan 19, 2011
583
11
Norman, OK
I mistyped
Code:
cd -
as
Code:
cd =
and it changed directory to root (C:\).
Wazapwidat?
 
Jan 19, 2011
583
11
Norman, OK
Looks to be related to extended search since I got
Code:
12:05:34 $ *cd /n =
TCC: (Sys) The system cannot find the path specified.
"="
Edit1:
but continuing on
Code:
0:00:00.003
[C:\Documents and Settings\qcmsb0\Desktop\Projects]
12:05:43 $ cd /=
TCC: (Sys) The system cannot find the path specified.
"/="
 
0:00:00.072
[C:\Documents and Settings\qcmsb0\Desktop\Projects]
12:07:51 $ cd \=
 
0:00:00.065
[C:\]
12:07:58 $ md =
 
0:00:00.002
[C:\]
12:08:17 $ cd \=
 
0:00:00.001
[C:\=]
12:08:19 $ cd ..
 
0:00:00.001
[C:\]
12:08:28 $ rd =
Edit2: Still might be extended search related?
 
Jan 19, 2011
583
11
Norman, OK
What are your fuzzy search options? Are you using Everything Search? Is this v14 or v15 (or both)? x86 or x64?
Extended Directory Search level 1 with path C:\MyProgramFiles\JPSoft\TCMD15.
No Everything search.
Both 14.03.59 and 15.0.21 on x86 XP SP3.

Here's a fresh run of TCMD
Code:
HTMLDump plugin v1.0.5 loaded.
ISO8601 plugin v1.3.7 loaded.
SafeChars plugin v1.7.0 loaded.
Snapshot v1.0.1 loaded.
TextUtils v0.62.1 loaded.
 
TCC  15.00.21   Windows XP [Version 5.1.2600]
Copyright 2013 JP Software Inc.  All Rights Reserved
Your evaluation period expires in 13 days.
You can buy Take Command at http://jpsoft.com
 
[C:\Documents and Settings\qcmsb0]
09:47:47 $ plugin /u *
 
[C:\Documents and Settings\qcmsb0]
09:48:01 $ *cd =
 
[C:\]
09:48:05 $
 
May 20, 2008
3,520
3
Elkridge, MD, USA
I have FuzzyCD=3. Same platform, not using Everything. The command *cd = in 15.0.22 pops up a window showing most (or all?) directories in JPSTREE.IDX. However, until I manually enlarged the pop-up height, it only displayed one entry.
 

rconn

Administrator
Staff member
May 14, 2008
11,005
98
I traced through the code, and this is an artifact resulting from (1) Windows considering a '=' to be a delimiter / space character, so (2) the wildcard routine (called by the fuzzy searches) considers it to be a terminating character (for example, in an executable extension comparison). So it matches directories with no filename; i.e., root directories.

Modifying this would potentially break a lot of things, so since it's not harmful (and since it's worked this way for at least 15 years without issue) I'm inclined to leave it as-is.
 
Jan 19, 2011
583
11
Norman, OK
In my situation, I found it by accident. Just reporting unexpected behavior so it doesn't bite somebody in the ass.