On Fri, 02 Apr 2010 09:12:16 -0400, rconn <> wrote:
|The problem isn't recognizing that there's a variable, the problem is that
|(1) TCC can't tell if you want it expanded now or later, and (2) at the time
|the TCMD.INI file is parsed, the TCC parser isn't yet capable of doing
|expansion (because there are a lot of .INI options that define subsequent
Except for TC button specifications, I can't think of a situation where I'd want
to use a variable name in the INI file and not have it expanded when the INI
file is read (wanting, rather, that it be expanded at some later time). Can you
give such an example?
Almost all the directives take values of "Yes". "No", a key name, or a number. I
doubt anyone is suggesting that environment variables be honored there. Only a
handful (or two) directives would seem appropriate for variable processing ...
Editor, log file names, start-up file locations, and perhaps MailAddress,
Comspec, StartDirectory (any others?).