That didn't seem to work very well (at least on my second attempt). My first try failed because I forgot your vital instruction to "make tab 1 your normal shell." When I tried explicitly to make Tab 1 run TCC I managed to conflubulate the whole Take Command and it wouldn't run at all any longer. I just got the dreaded "Not Responding" spinning wheel of death. I had to edit my INI file to yank out those menu-made mods before I could run TCC again.
Perhaps I'll abandon the idea and just run my command in a new tab after TCC is up and running ... as I have been doing. I had hoped to automate it a bit, but it's not worth very much time/trouble. Maybe one more attempt.
Maybe vince would like to capture the OPTION dialog about what a sample startup would be with te default shell and his editor in the 2nd tab. then tmaynard could change the paths / programs as necessary...
Hello? Vim? (Not GVim, but regular old console Vim.)
And I guess I should probably point out that if I were using Windows tools, I'd likely not be out on the command line in the first place -- but perhaps I should have a second cup of coffee on a rocky Monday morning before I post anything.
More to the point, I've tried emulating the suggested solution(s) and ended up with a scrogged TCC yet again. My own settings were:
Title: TCC 16.03
Command: C:\Program Files\JPSoft\TCMD16x64\tcmd.exe # With and without quotes
I chose to experiment "safely" by leaving TAB 1 blank and inserting the above into TAB 2. That failed miserably: I got only one tab (blank), and a non-responsive window. Ultimately, I could click/open a new tab and undo my changes (no manual editing of the INI required), but this simply isn't worth any more of my time.
My thanks to all who have responded. You are the giants upon whose shoulders I was unable to clamber up. Maybe next time. Thanks again.
That's definitely the problem. You're running the Take Command GUI, which is configured to run Take Command GUI in a tab, which is configured to run Take Command GUI in a tab, etc., etc., etc. tcc.exe is what gives you the console prompt.
Well, I guess I forgot to mention that I did indeed change "tcmd.exe" to "tcc.exe" and it had absolutely no ameliorative effect whatsoever; exactly the same hang as before, and this time I had to edit the INI file (with Notepad (!)), and logoff/on in order to recover.
After a lifetime of battling dragons I endeavor whenever possible to keep my systems as vanilla as possible -- sickeningly so -- so I doubt that this is a configuration issue (but it certainly could be, I won't rule it out).
Edit: What started out as just a hare-brained idea has escalated into near Yak Shaving status, and it's now burning cycles in brains other than my own. I never meant for any of this to happen. Forgive me, please.
No worries. Most of us are here to help too, not just report problems. :) Hmm... It should be pretty straight forward, given you're not trying to run TCMD inside itself. Heh My last suggestions would be to maybe rename your .ini file out of the way and then you'll be starting from scratch settings-wise. Maybe reboot too..? I do PC support and that's necessary more often than people would like it to be.
While I have reverted back to my everyday, production INI file each time (the one that's been working just fine for at least a year), I have not hidden it completely -- except for when I need to recover from a truly major foul-up here lately.
And, I did my time in the Tier 1 Help Desk trenches as well, and then served in Tiers 2 and 3 before they finally ran out of Tiers to put me on (and I had run out of tears, too), so I recognize the value of "turning it off and back on again." In fact, I do this religiously each and every day. "Dirty tables" cause as many problems as "faulty wires" do: My system never runs 24 contiguous hours, but it's only just another hoop so why not jump through it, eh? I'll do both and report back but be advised that the priority for me to acquire this bogey has dropped to zero.
In fact, in just another day or two the need to fire up TCC with a mysterious something running in a second tab will have dissipated.
Oh, and @Charles Dye: I owe you an apology, of course. First, I was a bit snippy when I made my wisecrack -- even though I tried to admit it at the time. It was uncalled for, and I regret it. Second, upon reflection, the truth in your remark is ineluctable: All of this code is compiled and linked against Windows libraries -- where else would it ever run? -- and thus even the console code can legitimately be said to be "Windows programs" ... Metro, Desktop, Commandline, ..., what have you. Let me run and refill that coffee cup of yours. It is coffee, right?
Will TCMD launch successfully with any true console app in its second tab? "Good" ol' CMD, for instance. If so, then I might tend to suspect something with your editor itself or a strange interaction between it and TCMD. (I'm assuming the editor loads without incident in a standalone instance of TCC.) If not, then...well, we'll have to keep looking for causes/answers. The folks here love a good TC*-related poser, even if your own interest is waning. Their success rate is very high.
And dang if that didn't work! I now have TCC running in Tab1 and <my secret> running right alongside in Tab2! AFAIK this only costs me a single tweak that I made manually to my INI file (to set <C-u> to be DelToBeginning). Obviously any other via-menu mods are also gone, but they can be restored as I notice their absence (Insert mode will be first! It always is.)
So thanks, TEA, for giving me that last-minute boost for yet one more attempt. And the fact that this time it worked really nags at me now: I must have made some silly little mistake on my earlier attempt. I've really don't nothing different (substantially speaking, that is) ... except probably configured it properly for the first time.
I will reveal the fact that my editor is not what I'm running in the second tab -- but no more! Actually, I do use Vim, and it's easy enough simply to have GVim running in another window and <M-tab> between the two, I wouldn't need console Vim in a second tab. It's all very hush-hush for now, I'm sorry.
Thanks again to all for the help, encouragement, and support. There is no "I" in "JPSoft" ... it's all about the team.