Strange behavior reloading SHRALIAS sav files.

May 20, 2008
11,287
95
Syracuse, NY, USA
I just installed TCC on a new machine (XP SP3). A logon script does this:

Code:
if not isdir %SHRALIAS_SAVE_PATH md %SHRALIAS_SAVE_PATH
cdd %SHRALIAS_SAVE_PATH

echo Now in %_cwd

for %f in ( *.sav ) %@name[%f] /r %f

delay 2

(with a few more delays later). The dirhistory file it loaded looked OK:

Code:
ff fe 47 00 3a 00 5c 00  50 00 72 00 6f 00 6a 00  ? G : \ P r o j
65 00 63 00 74 00 73 00  5c 00 67 00 6d 00 73 00  e c t s \ g m s
74 00 65 00 73 00 74 00  5c 00 52 00 65 00 6c 00  t e s t \ R e l
65 00 61 00 73 00 65 00  0d 00 0a 00 56 00 3a 00  e a s e . . V :
5c 00 0d 00 0a 00                                 \ . .

But it doesn't look good in the dirhistory popup, there being an unprintable in front of the first line.

Code:
?G:\Projects\gmstest\Release\
 
May 20, 2008
11,287
95
Syracuse, NY, USA
The new machine has nothing to do with it. It happens on the old machine also.

I just installed TCC on a new machine (XP SP3). A logon script does this:

Code:
if not isdir %SHRALIAS_SAVE_PATH md %SHRALIAS_SAVE_PATH
cdd %SHRALIAS_SAVE_PATH

echo Now in %_cwd

for %f in ( *.sav ) %@name[%f] /r %f

delay 2
(with a few more delays later). The dirhistory file it loaded looked OK:

Code:
ff fe 47 00 3a 00 5c 00  50 00 72 00 6f 00 6a 00  ? G : \ P r o j
65 00 63 00 74 00 73 00  5c 00 67 00 6d 00 73 00  e c t s \ g m s
74 00 65 00 73 00 74 00  5c 00 52 00 65 00 6c 00  t e s t \ R e l
65 00 61 00 73 00 65 00  0d 00 0a 00 56 00 3a 00  e a s e . . V :
5c 00 0d 00 0a 00                                 \ . .
But it doesn't look good in the dirhistory popup, there being an unprintable in front of the first line.

Code:
?G:\Projects\gmstest\Release\
 
Similar threads
Thread starter Title Forum Replies Date
Jesse Heines Strange Line Wrapping Behavior Support 14
N Fixed Strange dir behavior Support 6
P Strange mouse behavior with list Support 2
D Strange DO behavior with /O Support 5
M Strange behavior... Support 2
S Strange CHKDSK behavior Support 6
R strange bug? Support 7
F strange results Support 9
M Strange error messages from TCC in FTP copy Support 7
M Another possibly strange remote registry issue Support 5
forbin Strange handling of [nonbright] magenta background (v22) Support 2
vefatica REGDIR, strange error message Support 7
T WAD Strange Unexpected "features" in the Debugger Support 2
vefatica Strange tcc.exception.log Support 7
vefatica A strange one Support 0
Glenn Bowes Strange text at startup Support 5
Steve Pitts WAD Strange output from DEL of a non-existent directory Support 7
vefatica Big numbers, strange errors Support 1
aedthuio Strange... lpksetup Support 4
CWBillow dir /4 strange Support 2
D Strange issue with FOR loop Support 15
MikeBaas Strange prob with %@replace.. Support 4
vefatica OT: strange files in %TEMP Support 10
Dan Glynhampton Documentation v15 help: Strange links in @INT topic Support 0
R WAD Strange output from "memory" command Support 1
M Yet another strange something re something called "@TCONVERT" Support 8
Roedy How to? Strange colours Support 9
M WAD Strange "Start" misbehavior... Support 10
vefatica Very strange console font corruption Support 3
Steve Pitts Strange problem with FREE Support 10
A strange error in alias Support 9
newgeekorder Debugger IDE - strange tab and parameter behaviour Support 1
Exolon Strange Prompt. Support 6
vefatica Strange folders Support 1
T Strange CPU value Support 3
J Strange error: unset /s Support 14
CWBillow Strange happenings Support 2
B Strange handling of a .BAT file Support 5
J ASSOC / FTYPE strange error message Support 3
D Strange crashes in @CRC32 and @MD5 Support 9
Charles Dye Strange output, here-doc redirection, TYPE, //UnicodeOutput=Yes Support 6
vefatica Strange results with CP 1252 Support 12
S Strange REN problem - non-English characters Support 3
dcantor Strange status in ACTIVATE command Support 0
H @XMLNODES - New behavior? Support 3
H Behavior change re piping a string to a Java program Support 1
Jay Sage Baffling Behavior With TPIPE Support 5
D Pasting Unicode data has different behavior on TCC and CMD Support 2
P "Set" command behavior - a bug? Support 3
P LOG command behavior Support 3

Similar threads