Command lines interrupted with Ctrl-C are not recorded in the history (TCC 36, worked in TCC 28)

[SiggyBar]

In TCC 36, a command line that is interrupted with Ctrl-C is not written to the extended history (XHISTORY). In TCC 28, the same command line was recorded in the history log (TCHistoryLog). Command lines that end normally are recorded in TCC 36 as expected, also when they fail.

Versions:

• Works: TCC 28.02.18 x64 (history log)
• Broken: TCC 36.52.88 x64 (XHISTORY)
• Windows 11 [Version 10.0.26200.9457]

Clean reproduction: both versions launched from cmd.exe, with an empty INI file and a TCSTART path pointing to an empty directory. No aliases are defined. In both, I pressed Ctrl-C after three ping replies.

TCC 28, where the ping command line is recorded:

C:\Users\SigmundVik>C:\tools\JPSoft\TCMD28\tcc.exe @C:\tools\JPSoft\TCMD28\empty.ini //TCStartPath=C:\tools\JPSoft\TCMD28\nostart

TCC  28.02.18 x64   Windows 11 [Version 10.0.26200.9457]

C:\Users\SigmundVik>alias
TCC: No aliases defined

C:\Users\SigmundVik>echo tcc28
tcc28

C:\Users\SigmundVik>ping -t localhost

Pinging SIGMUND-PC [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

Ping statistics for ::1:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\Users\SigmundVik>tail /n 2 "C:\ProgramData\JP Software\Take Command 28\TCHistoryLog"
echo tcc28
ping -t localhost

TCC 36, where the ping command line is missing:

C:\Users\SigmundVik>C:\tools\JPSoft\TCC36\tcc.exe @C:\tools\JPSoft\TCC36\empty.ini //TCStartPath=C:\tools\JPSoft\TCC36\nostart

TCC  36.52.88 x64   Windows 11 [Version 10.0.26200.9457]

C:\Users\SigmundVik>alias
TCC: No aliases defined

C:\Users\SigmundVik>echo tcc36
tcc36

C:\Users\SigmundVik>ping -t localhost

Pinging SIGMUND-PC [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

Ping statistics for ::1:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\Users\SigmundVik>tail /n 2 "C:\ProgramData\JP Software\XHistory36"
2026-10-02 14:42:19|0.001|2|C:\Users\SigmundVik|alias
2026-10-02 14:42:23|0.000|0|C:\Users\SigmundVik|echo tcc36

Expected: a third entry for "ping -t localhost". It does not appear later either, also not after closing the TCC window. The same happens with "echo start && ping -t localhost", and with other programs ended with Ctrl-C.

If this change was intentional, could you please consider adding an option to record command lines that were interrupted with Ctrl-C, for example with their return code and the run time until they were interrupted? We often start servers from TCC and stop them with Ctrl-C after a short or long time. Those are exactly the commands we want to find and re-run from the history later, and right now they are never recorded.

Possibly related: thread 13105 (Ctrl-C after re-executing from the XHISTORY window, fixed in build 51). Here Ctrl-C itself works, but the interrupted command line is never written to XHISTORY.