tcc 36 closes unexpectedly

[drrob1]

I open tcmd 36 w/ several tcc 36 sessions, some starting in different directories by default.
Now I detach a tcc tab
and now I close tcmd because I only want this 1 tcc session open that I detached in the previous step.

Then 1-2 seconds after tcmd closes, the detached tcc window also closes, unexpectedly. This behavior did not happen on tcc 35 and earlier.

 

[rconn]

Are you detaching ConPTY tabs? That is not supported by Windows - a ConPTY session has to have its terminal handler running, or it will close (because there's nothing to handle it's I/O).

If you want to detach tabs, use the old-style hidden consoles, not ConPTY.

 

[drrob1]

I guess I was detaching a ConPTY tab.

What's a hidden console?

 

[rconn]

A hidden console is the v35 & earlier approach for tab windows - create a console window, hide it, and scrape the output to display on the TCMD tab window. When you create a tab window you can choose whether you want a ConPTY session or a hidden console session.

What you were doing when you Detach'd the ConPTY tab window was undocking / tearing off the tab, not disconnecting it completely from TCMD like the v35 hidden consoles.

 

[drrob1]

Do you mean that if I want to detach tabs, I should use v35?

 

[rconn]

If you want to detach tabs, you should not use ConPTY sessions. V36 allows you to use either ConPTY or hidden consoles.

You can tear off a ConPTY tab and move it around, but when you exit TCMD all ConPTY sessions will be closed.

 

[drrob1]

Do you mean the check box labeled "Run in Pseudoconsole (ConPTY)"

 

[rconn]

Yes. You can select or disable that option in two places - the Take Command configuration dialog (to set the default value), and in the Run dialog (to set it when starting a single tab window).

I never realized so many users were detaching tabs. Still unclear why they're doing it in most instances.

 

[drrob1]

I can only answer for myself. I was doing it because a detached window is compatible w/ vim.
I've discovered that a pseudoconsole is also compatible w/ vim so I don't need a detached tab anymore

 

[drrob1]

I'm going to modify that. At work, take command won't start without admin priv's. So I have to start individual tcc sessions. At work I'm running v 35 now, but I observed this behavior that tcmd won't start over multiple versions. No errors, just won't start.

 

[rconn]

I'm going to modify that. At work, take command won't start without admin priv's. So I have to start individual tcc sessions. At work I'm running v 35 now, but I observed this behavior that tcmd won't start over multiple versions. No errors, just won't start.

I don't understand what you mean by "tcmd won't start over multiple versions".

 

[drrob1]

I would double click the desktop shortcut for take command, and nothing would happen. I can't give you more information now as I'm not at work.
I do not have admin rights on that computer. For a short time I did, and it would start properly.
I don't know what's going on. Since I could start tcc, I do that at work.

 

[rconn]

That's almost always either your AV blocking TCMD from starting, or an app (also likely an AV) injecting faulty code into TCMD that's crashing it at startup. If it's your AV blocking it, it should be in your AV logs. If it's a bad code injection, it will probably be in the Windows Event log.

 

[drrob1]

I don't have access to those logs.
So it goes