Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

F7 file completion locks up, in both 33 and 28

Oct
29
0
Hi,

In version 33 and 28, when I type a partial filename and then hit F7, it shows the FileName popup box with title

"Filenames (not responding)", the letters that I typed, and only the first filename with that pattern.

After that, it just locks up, and it's necessary to shut down TCMD abruptly.

I also tried it with verson 28, and got the same result.

Edit: Just for the heck of it, I went way back to version 8, although it's not recommended for windows 10 or 11. But it works fine, without any lockups.


I'm using Windows 11 Enterprise.
 
Last edited:
Not reproducible here. I don't know where that "(not responding)" is coming from, but it's not from TCC.

What Filename Completion options have you set? (Go to OPTION / Command Line / Filename Completion).

Did you create any tab completion scripts (i.e., with TABCOMPLETE)?

Did you set the FILECOMPLETION environment variable?

Did you enable Everything Search (OPTION / Startup)?

Are you running any plugins?
 
Not reproducible here. I don't know where that "(not responding)" is coming from, but it's not from TCC.
I don't know how we came to that conclusion. The Task Manager is pointing to TCC.
What Filename Completion options have you set? (Go to OPTION / Command Line / Filename Completion).

See Attached. The Hidden options are checked.
Did you create any tab completion scripts (i.e., with TABCOMPLETE)?

Did you set the FILECOMPLETION environment variable?

No on both of these. Same with another PC that has tk33, but isn't having these problems with F7.
Did you enable Everything Search (OPTION / Startup)?

No, I don't want to use Everything.
Are you running any plugins?

No, we just installed this the other day. Unless there are some default plugins running.


See attached for more visual details.
 

Attachments

  • TCMD_F7_Lockup.pdf
    TCMD_F7_Lockup.pdf
    114.7 KB · Views: 2
  • tk_33_Lockup.webp
    tk_33_Lockup.webp
    15.7 KB · Views: 6
  • tk_CommandLine_Options.webp
    tk_CommandLine_Options.webp
    37.3 KB · Views: 6
  • Task_Manager_TCC_Lockup.webp
    Task_Manager_TCC_Lockup.webp
    12.7 KB · Views: 5
Strange that it draws one filename and then gorks. What's the next filename? test02.txt?

Do you see the same issue when running TCC in a standalone console window?
 
test02.txt, yes.

That's a good question. Confirmed, yes. Same result with tcc.exe

Well I confess I'm confused. I'm not seeing that issue here — Windows 11 Pro.

It's probably completely irrelevant, but what's that font you're using in Take Command?
 
MAYBE there is an influence of a security software - you could try to exclude the TCMD path (where you installed TCMD). I'm really not sure about that - but it could be worth a try ...
 
Thanks everyone,

Charles:
"It's probably completely irrelevant, but what's that font you're using in Take Command?"

Consolas/Bold/10

Ansi Colors on or off, doesn't matter. Foreground/Input/Error/Selected = Black, Background = White


rconn:
"Does this happen in other directories and / or drives?"

Everywhere, yes. Local drives and virtual drives.

"And does it hang if you use Tab (repeatedly) to complete the filenames?"

Tab works fine, it cycles through everything.


Alpengries:
"Remove tk 33 from the PATH."

Done, and same result.
 
fyi, I don't mind working with version 8 for the immediature future, I always liked the earlier versions, especially 6.
 
Back
Top