LOG command behavior

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Feb 27, 2018
11
0
#1
I cannot understand the LOG command behavior. First, I issue the "option" command and see:

1521202001135.png

Ok, then I issue the command:

log /H /W %TMP%\tcc.hst

followed by the "option" command again and see:

1521202189717.png

Now any command I type in TCC window is executed but is accompanied by the message:

TCC (Sys) System cannot find the path specified.
"C:\ProgramData\JP Software\Take Command 22\TCCommandLog"


This is 100% reproducable. Is this a bug?
 
#2
I tried it with TCC newly started after emptying all the boxes ... the same command "log /H /W %TMP%\tcc.hst". The option dialog then said:
1521215949116.png
That seems OK ... TCC correctly expanded %tmp% and enabled the history log. It seems to also enter a (default) command log name but not enable it (that's OK).

Afterwards, I had no problem entering commands. But it was not loggiing to h:\temp\tcc.hst. It was logging to "C:\ProgramData\JP Software\Take Command 22\TCCommandLog".

Even after restarting TCC, with these settings in place, it logged the history, but to the file specified for command logging.
1521216631966.png
Code:
v:\> type h:\4ntlogs\history.log
@option

v:\> tail /n 6 "C:\ProgramData\JP Software\Take Command 22\TCCommandLog"
echo foo
echo bar
type h:\temp\tcc.hst
type "C:\ProgramData\JP Software\Take Command 22\TCCommandLog"
type h:\temp\tcc.hst
tail /n 6 "C:\ProgramData\JP Software\Take Command 22\TCCommandLog"
 
Feb 27, 2018
11
0
#3
This is the next thing I wanted to report - nothing is written to the file that is the argument to the "log /H" command.
Nobody thinks TCC does not expand environment variables. It does. I just expected the (really clever, useful, etc.) behavior declared in the documentation. If TCC does not follow the described behavior then it is a bug, isn't it?

In parallel, I am using the 4NT born approx. 15 years ago. Comparing TCC and that old 4NT, the modern TCC is a buggy, almost unusable thing. Usually I find a bug in each command I try to use... Looks like the product never passed the testing procedures.
 
#4
This is from a newly started TCC, having done nothing else.
Code:
v:\> grep -i log %_ininame
HistLogName=H:\4ntlogs\history.log
HistLogOn=Yes
LogAll=No
LogOn=No
LogErrors=No

v:\> tail /n 5 h:\4NTLogs\history.log
@option
log /h /w h:\4ntlogs\history.log
echo foo
type h:\4NTLogs\history.log
@option

v:\> tail /n 5 "C:\ProgramData\JP Software\Take Command 22\TCCommandLog"
grep -i log %_ininame
grep -i log %_ininame
type h:\4NTLogs\history.log
tail /n 5 h:\4NTLogs\history.log
tail /n 5 "C:\ProgramData\JP Software\Take Command 22\TCCommandLog"
If, after that, I look at the option dialog, I see
1521218178260.png