multi-INI file merging

Apr 2, 2011
1,441
10
54
North Carolina, USA
I have TCMD v 8 to 12.1 and have one INI file for each TCMD and TCC; Hence I'd like to merge them into one ALL_TCMD.INI and ALL_TCC.INI files. Not sure what is the best way to do this? I am not saure even how to structure the ALL_*.ini files to check for different versions. Would it be using %_4ver or similar? Any suggestions are welcomed.

D:\TakeCommand\INIs\TCC_v9.ini
D:\TakeCommand\INIs\TCC_v10.ini
D:\TakeCommand\INIs\TCC_v11.ini
D:\TakeCommand\INIs\TCC_v12.ini
D:\TakeCommand\INIs\TCMD_v8.ini
D:\TakeCommand\INIs\TCMD_v9.ini
D:\TakeCommand\INIs\TCMD_v10.ini
D:\TakeCommand\INIs\TCMD_v11.ini
D:\TakeCommand\INIs\TCMD_v12.ini


TCC 12.10.64 Windows XP [Version 5.1.2600]
TCC Build 64 Windows XP Build 2600 Service Pack 3
Registered to Charles Galloway - 5 System License

========================================
 
May 20, 2008
3,515
4
Elkridge, MD, USA
---- Original Message ----
From: Charles G
| I have TCMD v 8 to 12.1 and have one INI file for each TCMD and TCC;
| Hence I'd like to merge them into one ALL_TCMD.INI and ALL_TCC.INI
| files. Not sure what is the best way to do this? I am not saure even
| how to structure the ALL_*.ini files to check for different versions.
| Would it be using %_4ver or similar? Any suggestions are welcomed.
...
Sorry, but neither 4NT (v8), nor TCC/TCMD(v9+) are able to select portions of an .INI file based on version. The only selection is based on section title, which allows separating directives meant for the command processor (4NT/TCC) from those meant for the GUI shell (TCMD). The closest you can get to your goal is the use of the INCLUDE directive (which is deprecated by Rex) and put directives that are valid in all versions of interest into one file, those valid since V9 into another, those valid since V10 into yet another, etc. - and you must also worry about directives valid only in earlier versions. One of the issues about using .INI files by the INCLUDE directive is that if if you make changes with the OPTION dialog, it merges all directives from included files into the file named in the _ININAME internal variable, without updating the included files. Lastly, using 4NT/TCC updates the .INI file even without using the OPTION dialog by adding sections relating to the debugger, etc. - unless the files are write-protected.

The only method you could use, other than include files, that sets options based on 4NT / TCC version is the use of the OPTION @FILE format in your 4START / TCSTART, where you can call files of directives based on the 4NT / TCC. However, some directives are processed only from the .INI file(s) processed when 4NT / TCC is loaded, BEFORE the 4START / TCSTART is executed, and cannot be set or modified once the command processor started.

It is due to the complexity of processing directives and all the above mentioned restrictions (and there may be more I did not report) that Rex chose no longer to document any directives that can be set by the OPTION dialog.
--
HTH, Steve
 
Similar threads
Thread starter Title Forum Replies Date
D How to use multi-line DO to loop through first level directory names Support 5
rps Multi-column DIR /v not displaying all files. Support 5
vefatica FFIND and multi-line regular expressions Support 4
D xp support and multi-license Support 5
T WAD Difference between TCC and CMD in handling multi-command lines Support 6
V V - Multi-Pane File Manager Support 14
Daniel P How to Purchase a Multi-System License for TCC? Support 2
B Alias with multi line definitions not assigned Support 6
T Fixed multi-line alias issue Support 13
T Closing multi-tab TCMD crashes Support 4
D Individual vs multi-system licenses Support 1
C Language setup files, to use in creating similar for Multi-Edit Support 2
vefatica Single-line DO inside nested multi-line DOs? Support 9
C How to? Multi-Display Configuration Support 5
G Documentation on TCMD.INI Support 9
RChrismon How to? Copy TCMD.INI to New Version Support 7
vefatica Documentation INI file location? Support 2
D Custom ini-file is not read, by tcmd.exe cli Support 6
Alpengreis Fixed New INI directive "ANSIWin10" is invalid Support 2
Alpengreis TCMD.INI: The "super hidden" problem ... Support 6
D Fresh instance of TCMD does not use TCMD.INI Support 7
C Optimum Placement for TCMD.ini and others? Support 6
cgunhouse Documentation Locating the TCMD.INI File Support 9
D V19: toolbar /r "path\tctoolbar.ini" Support 1
B Fixed Error messages from TCMD.INI Support 2
C tcmd.ini not loading from program dir? Support 5
Detlef Fixed ParameterChar in TCMD.INI no longer working Support 35
Jay Sage Toolbar Update to INI File Not Working Support 10
Jay Sage How to Determine INI File Used by TCMD Support 6
Jay Sage Unable to Specify INI File Support 19
A How to? TCC/LE: How do you add "edit-mode=insert" to ini file? Support 9
D How to? Using a custom ini file with TCC from Take Command Support 7
cgunhouse TCMD.INI Issue Support 7
Fross TCC INI Support 2
Jay Sage Specified INI File Refuses to Run Support 3
T TCTOOLBAR /C & TCTOOLBAR /I should reload toolbar from TCMD.INI, right? Support 1
T TCC reading TCMD.INI causing "Invalid item name" warnings and pauses Support 2
D ini directives and @select example in Help Support 0
nickles Reload tcmd.ini from the command line Support 11
deleyd How to? Alias in TCMD.INI file? Support 2
J Extended directory search - cure by renaming tcmd.ini Support 10
A How to? How to enable UTF-8 output in tcmd.ini Support 9
C Env vars in tcmd.ini Support 12
S Location of tcmd.ini in x64 Support 4
M HistoryExclude .INI directive Support 2
williamleara Specifying path to TCMD.INI causes issues Support 8
R location of .ini file Support 17
C starting tcmd with alternate INI file Support 15
E Environment variable in tcmd.ini Support 14
R Toolbar - save to .INI Support 4

Similar threads