Q: Were any there after the install but before you launched anything?Well, even though I had shut down ShrAlias before updating, after updating to build 51 and launching TCMD, there were two copies of ShrAlias running. Now, I did not discover this until after opening some additional tabs, so I don't know that two copies appeared immediately.
v:\> shralias & shralias SHRALIAS loaded SHRALIAS loaded v:\> tasklist | grep -i shra 5504 ShrAlias ShrAliasWindow 4516 ShrAlias ShrAliasWindow
v:\> shralias & echo %_shralias SHRALIAS loaded 0
Hmmm.... Perhaps Take Command should have an option to automatically start SHRALIAS before any tab windows?Jay, how many startup (TCC) tabs do you have defined? If one tries to start SHRALIAS too soon after another does, the second one won't be able to figure out that SHRALIAS is already running. It's quite easy to start two instances of SHRALIAS if you do it quick enough.
@echo off if %_pipe == 1 .or. %_transient == 1 quit iff %_shralias == 0 .and. %_tctabactive == 1 then shralias history /r "%@path[%@full[%0]]cmdhist.txt" dirhistory /r "%@path[%@full[%0]]dirhist.txt" alias /r "%@path[%@full[%0]]aliases.txt" function /r "%@path[%@full[%0]]functions.txt" alias desk:=%@shfolder alias docs:=%@shfolder alias drop:=%USERPROFILE%\Dropbox endiff ... ...
It's a matter of timing, so it being one way in one version and another way in another version is not a conclusive argument that something's wrong. IIRC, the check for a running SHRALIAS is a check for the existence of a window; if the check is made too soon, the window won't exist. Jay, does your TCSTARY cause any transient or pipe instances of TCC to be started? If so, check for that in TCSTART as in Rod's example.TCMD starts only one TCC tab, which launches ShrAlias if it is not already running. Also, I never had this problem before version 17, and my configuration has not changed in any substantive way. As I wrote earlier, I will try to remember to watch things very carefully with future updates.
cdd %SHRALIAS_SAVE_PATH do c in /L history dirhistory alias function ( %c /r %c.sav ) shralias delay 2
I did not notice any TCC sessions sessions before TCMD opened and my one tab loaded. If Rex is running TCC sessions to finish the install, they should do something to avoid using the user's INI file and certainly the TCSTART script. I also don't know why more than one instance of TCC would be used (but, then again, I don't really have much of an idea about what happens during the installation).Curious ... did you notice if TWO TCCs were started (to handle the registration dialog, before TCMD)?
So what is happening in the installer to kill and then reload ShrAlias? All I'm doing is running the installer. ShrAlias was gone before I clicked the button to start Take Command, and the two copies appeared before the registration screen came up.TCC is not used at all during installation. (Nor is TCMD, IDE, or SHRALIAS.)