On Mon, 12 Sep 2011 20:11:44 -0400, rconn <> wrote:
|---Quote---
|> TCC 11 also terminates immediately. And TCMD (v13) terminates
|> immediately when X'ed if TCC v11, CMD, or PS is the only thing
|> running in a tab.
|---End Quote---
|Assuming that TCC 11 is running with the same configuration as 12 and 13,
|that would mean that it is a TCC issue and doesn't have anything to do with
|TCMD.
I'm pretty confident all the settings are the same. The ones that have affected
this in the past (UpdateTitles=No, TITLEPROMPT set, TCEXIT existing) are the
same. BTW, the more recent problem (tab-TCC not terminating right away goes
away if I first "UNSET TITLEPROMPT" (and I'd bet if I did any of the other
measures that affected my earlier, similar problem).
Hmmm!, it doesn't happen when TCC is running stand-alone, so it has something,
however indirect, to do with TCMD or with the mere fact that it's hidden.
What happens when the user X's a tab (or X's TCMD)? Do you send
WN_SYSCOMMAND\SC_CLOSE to the console? Are you sure it's sent right away? With
a plugin, I could have TCC send WM_SYSCOMMAND\SC_CLOSE to itself after it has
been hidden.