|| IMHO if TCMD's .INI file is explicitly specified, AND that file does
|| not specify any tabs, the default TCC tab ought to use the same .INI
|| file as its parent TCMD. Anything else will cause the confusion of
|| the OP, esp. since TCMD includes a pull-down menu item to modify
|| TCC options.
| ---End Quote---
| That would be reasonable, except (1) there's not really any such
| thing as a "default TCC tab"; (2) if you're changing the default
| .INI for TCMD, there's no particular reason to think you also want
| to change it for TCC; (3) there's currently no way for TCC to query
| a parent TCMD process for the .INI file; and (4) there isn't any
| reason to put the TCMD.INI file anywhere other than %localappdata%
| except "because I want to".
As I am far too keyboard oriented, and open and close at least two versions
of TCC many times an hour, I am not normally a user of TCMD, thus my view is
virtually that of a newbie.
(1) If you are a new user and just installed and started TCMD, it does
open with a single tab. AFAIK that tab runs TCC.EXE, and is what I referred
to as the "default TCC tab".
(2) is valid, but should probably be documented (a warning in the
section that specifies how to change TCMD's .INI that this does not affect
(3) is valid, but irrelevant - whatever .INI was used to start TCC is
the only one it will modify using OPTION dialog. If it is also the parent
TCMD's .INI file, life for newbies is simpler.
(4) is invalid for portable ("TC on the stick") users, and for permanent
users is valid only for those who only use a single version and never use
TCC to perform special actions depending on which shortcut file started it.
Keeping .INI files together with the TCSTART.BTM files for each special use,
often in a directory containing other programs utilized reduces maintenance
complexity. I have more than 14 shortcuts which utilize TCC for specific
purposes (not interactively). These use several different .INI files, not
located together. It is also much easier to transfer the files from one
system to another where the %localappdata% path is different.