Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Elapsed time format in prompt changed in TCC 25

Dec
10
0
Hi,

I upgraded from Take Command / TCC v24 to v25 and noticed that formatting (and value calculation) of elapsed time ($=) in prompt has changed.

Old format in v24 was "1.22.33,44". New format seems to be "1223344". In addition, the value does not make sense.

Help in v25 says
=The elapsed time (in milliseconds) since the previous command was started.


However, even simple "echo foo" commands gives value over 80000 (80seconds?).

See a screenshot (from http://tkoskine.me/tcc/tcc-24-vs-25-prompt-2019-09-03.png)
tcc-24-vs-25-prompt-2019-09-03.png



Prompt is set to
PROMPT=$e[1;35m[$e[1;36m$m $e[1;32m%LOGONSERVER%$e[0m$b$r$e[1;35m]$e[0m $~ ($=)$_$e[1;35m%@printftp[]%@execstr[perl c:\work\scripts\vcs-detect.pl]$e[0m$g


I assume this is either a documentation or code implementation bug? The elapsed time value in v25 would make sense if it is in microseconds.
 
I don't see anything like that. What is your PROMPT variable?

1567533913972.png
 
Same problem with simpler prompt:

v24:
> prompt $p $= $g

c:\work 0.00.00,00 >
c:\work 0.00.00,82 >
c:\work 0.00.01,15 >
c:\work 0.00.01,41 >
c:\work 0.00.11,19 >
c:\work 0.00.11,37 >ver

TCC 24.02.50 x64 Windows 10 [Version 10.0.18362.295]

c:\work 0.00.00,00 >


v25:
> prompt $p $= $g

c:\work 12067 >
c:\work 6440684 >
c:\work 6871349 >
c:\work 7775893 >
c:\work 7954276 >
c:\work 8131215 >
c:\work 8332007 >
c:\work 8498167 >ver

TCC 25.00.16 x64 Windows 10 [Version 10.0.18362.295]

c:\work 12581 >


I am running Finnish version of Windows 10, if that matters.
 
> I am running Finnish version of Windows 10, if that matters.

Time and decimal settings in TCC seem to matter.

I see the above behaviour if I set Localication /Time to Country, Decimal to Auto and Thousands to Auto.

Setting Decimal and Thousands to "Period" I get same view as vefatica:
> prompt $p $= $g

c:\work 0.013 >
c:\work 0.719 >
c:\work 1.17 >
c:\work 1.69 >
c:\work 2.129 >
c:\work 2.366 >
c:\work 2.558 >
c:\work 2.966 >echo foo
foo

c:\work 0.018 >echo foo
foo

c:\work 0.013 >echo foo
foo

c:\work 0.029 >echo foo
foo

c:\work 0.013 >echo foo
foo

c:\work 0.012 >echo foo
foo

c:\work 0.012 >echo foo
foo

c:\work 0.012 >echo foo
foo

c:\work 0.013 >echo foo
foo

c:\work 0.013 >echo foo
foo

c:\work 0.012 >
 
One more example, with options:

TCC v24:
> prompt $p $= $g

c:\work 0.00.00.01 >
c:\work 0.00.00.56 >
c:\work 0.07.01.59 >setdos /g,

c:\work 0.00.00,01 >setdos /g.

c:\work 0.00.00.00 >setdos /g-

c:\work 0.00.00,00 >setdos /gx

c:\work 0.00.00,00 >setdos /gfoo

c:\work 0.00.00,00 >setdos /g,,

c:\work 0.00.00,00 >setdos /g.

c:\work 0.00.00.00 >

TCC v25:
> prompt $p $= $g

c:\work 0.012 >setdos /g,

c:\work 32885 >setdos /g.

c:\work 0.018 >setdos /gx

c:\work 12124 >setdos /g;

c:\work 16821 >setdos /g.

c:\work 0.013 >setdos /g-

c:\work 12799 >setdos /gfoo

c:\work 12045 >
 
Yes, same problem there.

TCC v25:
> prompt $p $= $g

c:\work 11806 >timer
Timer 1 on: 18.22.46

c:\work 11985 >echo foo
foo

c:\work 12769 >timer off
Timer 1 off: 18.22.50 Elapsed: 0.00.04,11403

c:\work 12337 >setdos /g.

c:\work 0.012 >timer
Timer 1 on: 18.22.58

c:\work 0.012 >echo foo
foo

c:\work 0.013 >timer off
Timer 1 off: 18.23.01 Elapsed: 0.00.03.119

c:\work 0.012 >
 

Similar threads

Back
Top