TEE resets text colors for previously displayed text to default colors

[MGibs]

Running the following command in TCC displays text with a red background.

color bright white on red & echo Hello there & color bright white on blue

Running a subsequent command which pipes text through TEE, resets the text colors to the default bright white on blue in the TCC window.

 

[vefatica]

Not here.

 

[Jay Sage]

I basically see what Vince sees, but with one exception: The next line after foo gets the color.

Any idea why that is happening?

 

[MGibs]

I basically see what Vince sees, but with one exception: The next line after foo gets the color.

View attachment 6156

Any idea why that is happening?

I saw the same thing happen with the extra red line, but only when my input cursor was at the bottom of the tcc window. If I did a CLS first, so the input cursor was at the top, then it looked like Vince's screen. I didn't want to complicate the issue I was reporting, since this behavior also happened in Version 35, so not new to V36.

 

[Eric Pement]

Here is what I get. My background and foreground color scheme is the default.

 

[MGibs]

Thank you for testing my issue Vince and Jay and Eric. I noticed that in all of your screenshots TCC was using the default Output color of white on black.

I had my TCC Options setup for Output to be bright white on blue

I also had the following line in my TCStart.

color /a bright white on blue

This was there because without it my TCC screen looked like this when it initially loaded.

So I reset my TCC options to use the default colors for output, and removed the Color command from my TCStart.

And then I got the same results that you did from executing these two lines.

So far so good.

So I then executed these lines

Color /A bright white on blue
color bright white on red & echo Hello there & color bright white on blue
echo Goodbye color | Tee e:\TestTee.txt

And everything worked as expected.

So I added the same "Color /A bright white on blue" command back to my TCStart and closed/reopened Take Command.
Then I executed the same test:

color bright white on red & echo Hello there & color bright white on blu
echo Goodbye color | Tee e:\TestTee.txt

I got my same problem results where the Red text was recolored White on Blue text.

I'm not sure why the "Color /A" command run as part of TCStart would generate any different results than executing it at the command line immediately after TCC starts...but it appears to be doing just that.

@rconn - are you able to reproduce the "issue" I am seeing, and am I doing something I shouldn't be [again]?

Also, if I set my output colors in TCC Options as I originally had them, is it expected for TCC to load as it originally appeared in my second screenshot - with just the output text on a blue background and the rest of the "whitespace" with a black background?

 

[Jay Sage]

I saw the same thing happen with the extra red line, but only when my input cursor was at the bottom of the tcc window. If I did a CLS first, so the input cursor was at the top, then it looked like Vince's screen. I didn't want to complicate the issue I was reporting, since this behavior also happened in Version 35, so not new to V36.

Indeed. I guess I'm usually working at the bottom of the tab window. After a CLS, I can execute the command line over and over, and the output looks fine until it reaches the bottom of the screen.

That looks like a bug, but it may not be something Rex can do anything about.

 

[vefatica]

They're not defaults for me. I define RGB values in the OPTION dialog which jive with a custom 20-color palette (16 + FG, BG, selection BG, and cursor) which I set in TCStart.BTM.

 

[MGibs]

OK, just figured out my issue. The problem, as I feared, was self-inflicted.

Found this in the help for TCStart

"Pipes, Transient Sessions / Processes, and TCSTART

When you set up the TCSTART program, remember that it is executed every time the command processor starts, including when running a pipe or when a transient copy of TCC is started with the /C startup option."

So I looked closer at my TCStart.BTM and realized somewhere along the way I commented out this line near the beginning:

if %_pipe != 0 .or. %_transient != 0 quit

I uncommented the line and all was working as expected again. Sorry for all the noise on this.