Long commands retrieved from command history have blank line when wrapped

[RogerB]

TCC (x64) Version 26.02 Build 42 [26.02.42]
Microsoft Windows 10 Pro (2004) [10.0.19041.388]

I think this problem started with build 42 (possibly a side effect of the fix for no line wraps at the bottom of the screen buffer). It doesn't happen in version 25, but I haven't gone back to build 41 to confirm if it happens there. The problem occurs both in standalone TCC windows and TCC tabs within TCMD.

If there is a long command in the command history which, when recalled is longer than the width of the TCC window, a blank line appears in the command when it wraps. As an example, if I do a directory command for with a file that has a longish path and name...

d:\>dir /b c:\Windows\System32\DragDropExperienceCommon.dll
DragDropExperienceCommon.dll

Then I make the TCC window narrower such that the above command line has to wrap, and press the UP arrow to retrieve the command from history, a blank line appears:

d:\>dir /b c:\Windows\System32\DragDropExperienceComm

on.dll

 

[Alpengreis]

Here, it works correctly with same system and TCMD version as you, tried in TCC:

 

[TinuSystem]

I have the same problem, Also when I paste a long content from clipboard, the text is show as

 

[vefatica]

Happens for some; doesn't happen for others. We need to figure out how to MAKE it happen or PREVENT it from happening. Any ideas?

 

[vefatica]

TinuSystem, in your experiment, how did the text get into the clipboard?

 

[TinuSystem]

Copied (CTRL-C) in Texteditor (Textpad). If I paste with SHIFT-INS the result is:

and when I get the command from history (CURSOR UP):

It's only a 'display problem', the command is executed correctly. (ps: unknown command is correct. the programm tf.exe does not exist on that location)

 

[TQ5]

I have exactly the same problem. I have Take Command v26.02.43 x64.

Here's what happens when I type the command and then type the file:

This makes it difficult to correct typing since the cursor is above the text. According to my TakeCommand (check for updates), my software is up to date, and Windows 10 is up to date (version 10.0.19042.685).

This makes TakeCommand more difficult to use. What can be done? Thanks.

 

[Rodolfo]

In my case I paste a long command line from clipboard and it seems good and is executed correctly.
When I press arrow-up to recall that line there are empty lines and the cursor is in the middle of them.
I have "TCC 27.00.16 x64 Windows 10 [Version 10.0.19042.685]".

Regards

Rodolfo Giovanninetti

 

[rconn]

I cannot reproduce that here (TCC 27.00.17, Windows 10.0.20279.1).

 

[Charles Dye]

Does this happen in the legacy console mode, the new console mode, or both?

 

[TQ5]

I am having the same problem (see screenshots above) and I'm not sure how to check whether I'm in legacy console mode or new console mode(see comment from December 22, TQ5). I have TC v26.02.43 x64, and it is the current update of V26. Thanks for your help.

This does not occur in my version of TC v22.00.40 x64 on a Surface Pro 7.

 

[Charles G]

@TQ5
From Legacy Console Mode – Windows Desktop - Windows Console
"
To use Legacy Console mode, first open any console hosting window. This is typically done by launching one of the command interpreters CMD or PowerShell.


Right-click on the application title bar and choose the Properties menu option. Choose the first tab, Options. Then check the box at the bottom of the page describing Use legacy console. Press the OK button to apply.


The setting can be reverted by returning to the same property sheet menu and unchecking the box then pressing OK."

 

[Charles Dye]

@TQ5
From Legacy Console Mode – Windows Desktop - Windows Console
"
To use Legacy Console mode, first open any console hosting window. This is typically done by launching one of the command interpreters CMD or PowerShell.


Right-click on the application title bar and choose the Properties menu option. Choose the first tab, Options. Then check the box at the bottom of the page describing Use legacy console. Press the OK button to apply.

And after that, I think you need to close and restart the console program. Or close and restart Take Command. I think that setting is only checked when starting a console program -- though I could be mistaken.

 

[RogerB]

Does this happen in the legacy console mode, the new console mode, or both?

I'm still seeing this problem on v27 (having originally reported it on b42 of v26), it happens in both legacy and new console modes.

 

[TQ5]

Thanks for the suggestion. Changing in and out of legacy mode didn't make a difference for TC v26.02.43 x64.
The problem described above (a blank line between two parts of a command line that is too long. does not occur in my version of TC v22.00.40 x64 on a Surface Pro 7.

 

[TQ5]

SOMEWHAT GOOD NEWS. I uninstalled V26.02.43 x64 and installed the previous version v26.01.40 x64 and I don't have this problem. As noted, I didn't have in in V22 so it is a bug introduced after V26.0.140. Hope this helps them figure it out

 

[mwthomasjr]

I have the same issue with TCC 27 (TCC 27.00.18 x64). It happens when pasting a filename from explorer or just using completion. Any wrap adds the blank line. If you change the command line with the arrows to a different line in history, and the other entry is only one line the 2nd line does not get removed. It happens within Take Command or in a console window.

 

[TQ5]

For me, V 26.02.43 x 64 and TC 22 (on another computer) did not have this problem. Since this is an ongoing problem, I wish JP Soft would do something. I will not upgrade until I know this is fixed in the newer version.
I would like to know how to directly ask JP Software.

 

[Charles G]

For me, V 26.02.43 x 64 and TC 22 (on another computer) did not have this problem. Since this is an ongoing problem, I wish JP Soft would do something. I will not upgrade until I know this is fixed in the newer version.
I would like to know how to directly ask JP Software.

Either email support (at) jpsoft.com or tag @rconn

 

[TQ5]

@rconn
Thanks for the helpful reply, Charles. I e-mailed [email protected] and haven't heard yet, but it has only been a week.
For me, V 26.02.43 x 64 and TC 22 (on another computer) did not have this problem. Since this is an ongoing problem, I wish JP Soft would do something. I will not upgrade until I know this is fixed in the newer version.

 

[rconn]

If you change the default output color do you still see the problem?