TCC 9.02.152 truncated error messages

[Stefano Piccardi]

I set the error color directive (Error Foreground Bright White and Background Bright Red in the Windows tab of the TCC properties dialog - command OPTION).
When a system or shell or ECHOERR message wider than the console window is output, TCC truncates the message text instead of wrapping it around. Sometimes it does wrap it around, but incorrectly, so the message always partly illegible.
Can this annoying behavior be fixed? I can't figure out the error message, especially if a filepath is listed.
When the error color directive is unset, TCC wraps the error message correctly. However, I would much prefer not to have to give up using this useful directive.
Versions: TCC 9.02.152 - Windows XPPro SP3

 

[Jim Cook]

TCC 9.02.152 truncated error messages

TCC 10.00.41 Windows XP [Version 5.1.2600]
TCC Build 41 Windows XP Build 2600 Service Pack 3
Both inside TCMD and stand alone.

I get a different behavior. Mine wraps, but the prompt comes back in the
middle of the output.

The email below will look bad, but here's a summary of what I see: My
original command, two lines from the output, the prompt overwriting the
third line of output, the fourth and last line of output.

Like:
C:\>echoerr %@expand[*]
!BCKOF-Telnet-LU01.R1W...
m.cnf AKS100MB.devices ...
C:\>b.netcnf.txt AKS100MB.PACKAGE.ZIP...
AKS100MBDISK.SBR...


Actual:
C:\Develop\KESTREL\SYSGENS>echoerr %@expand[*]
!BCKOF-Telnet-LU01.R1W !BCKOF.CNF !BCKOF.TAPE AKS100MB.ANS AKS100MB.BLD
AKS100MB.cmd aks100mb.cnf aks100mb.custo
m.cnf AKS100MB.devices AKS100MB.DOC AKS100MB.LU01.TELNET.r1w
AKS100MB.LU02.DISK AKS100MB.LU31.DISK AKS100MB.LU40
C:\Develop\KESTREL\SYSGENS>b.netcnf.txt AKS100MB.PACKAGE.ZIP
aks100mb.readme.txt AKS100MB.SETUP_PORTS.CMD aks100
mbdisk.c AKS100MBDISK.EXE AKS100MBDISK.map AKS100MBDISK.OBJ AKS100MBDISK.SBR
make.bat serialcables.cnf standard.
cnf sysgens.mak update.bat vc60.pdb vcs.cfg


On Wed, Jan 28, 2009 at 2:49 AM, Stefano Piccardi <>wrote:

> I set the error color directive (Error Foreground Bright White and
> Background Bright Red in the Windows tab of the TCC properties dialog -
> command OPTION).
> When a system or shell or ECHOERR message wider than the console window is
> output, TCC truncates the message text instead of wrapping it around.
> Can this annoying behavior be fixed? Very often I just can't read figure
> out the error message, especially if a filepath is listed.
> When the error color directive is unset, TCC wraps the error message
> correctly. However, I would much prefer not to have to give up using this
> useful directive.
> Versions: TCC 9.02.152 - Windows XPPro SP3
>
>
>
>
>

--
Jim Cook
2009 Saturdays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Sunday.

 

[rconn]

Stefano Piccardi wrote:

> I set the error color directive (Error Foreground Bright White and Background Bright Red in the Windows tab of the TCC properties dialog - command OPTION).
> When a system or shell or ECHOERR message wider than the console window is output, TCC truncates the message text instead of wrapping it around.
> Can this annoying behavior be fixed?

Not without breaking several other things. I'll put it on the
suggestion list for v11.

Rex Conn
JP Software

 

[dcantor]

I set the error color directive (Error Foreground Bright White and Background Bright Red in the Windows tab of the TCC properties dialog - command OPTION).
When a system or shell or ECHOERR message wider than the console window is output, TCC truncates the message text instead of wrapping it around. Sometimes it does wrap it around, but incorrectly, so the message always partly illegible.
Can this annoying behavior be fixed? I can't figure out the error message, especially if a filepath is listed.
When the error color directive is unset, TCC wraps the error message correctly. However, I would much prefer not to have to give up using this useful directive.
Versions: TCC 9.02.152 - Windows XPPro SP3

Yes, I've seen this behavior, too, but thought it was related to running a command line program. When I've needed to see the actual error message, I've gone to the error logfile.

I just reproduced this on TCC 10.00.41 as well.