Page 1 of 1
External editor for TC config files
Posted: 2007-05-12, 10:03 UTC
by StatusQuo
With Config / Change Config Files Directly you can comfortably call the TC settings files into an editor.
But the use of notepad.exe seems to be hardcoded here (?).
I have set an external editor in TC and even assigned the extension INI to be opened by it.
But TC still calls notepad.exe to edit its config files.
Suggestion:
IMO it would be better to load them to the user-configured external editor instead (if present),
to use its syntax highlighting, multiple files in one window, etc.
If the configured entry for external editor is invalid (file not found) notepad could be used instead.
Workaround I use right now:
I've configured an entry in dir menu to open the files with the external editor.
Posted: 2007-05-12, 10:28 UTC
by Alextp
Posted: 2007-05-12, 10:51 UTC
by StickyNomad
2
StatusQuo
Support+
I also have an own menu entry to open the INIs in my favorite editor, or use the UTC editors. But an option like...
Code: Select all
ConfigChangeIniFilesExternalEditor=[0|1]
...that would use the defined F4-editor when cm_ConfigChangeIniFiles is invoked would indeed be nice.
Not vital of course, but a useful little addition IMO. So at least some users (2 so far
) won't need custom menu entries for that anymore.
Re: External editor for TC config files
Posted: 2007-05-12, 14:45 UTC
by wanderer
StatusQuo wrote:Suggestion:
IMO it would be better to load them to the user-configured external editor instead (if present)
Yup, this has been requested again and i fully support it.
Re: External editor for TC config files
Posted: 2007-05-12, 19:03 UTC
by m^2
wanderer wrote:StatusQuo wrote:Suggestion:
IMO it would be better to load them to the user-configured external editor instead (if present)
Yup, this has been requested again and i fully support it.
I said before, but: support+=2;
Posted: 2007-05-13, 16:46 UTC
by Stance
StatusQuo wrote:I have set an external editor in TC and even assigned the extension INI to be opened by it.
The TC config file can have another extension:
http://www.ghisler.ch/board/viewtopic.php?p=63488#63488
StatusQuo wrote:But TC still calls notepad.exe to edit its config files.
The reason is: User can use a HEX-Editor or something else in F4, unsuitable to edit INI -files.
StatusQuo wrote:Suggestion:
IMO it would be better to load them to the user-configured external editor instead (if present),
to use its syntax highlighting, multiple files in one window, etc.
My support for this request, especially tabbed editors could be very useful for this task !
StatusQuo wrote:Workaround I use right now:
I've configured an entry in dir menu to open the files with the external editor.
So did I, in v7 a em_command to open the
current config file for every instance.
Put the path to your editor and use "%commander_ini%" as parameter in the command -field. (See Code)
StatusQuo wrote:But the use of notepad.exe seems to be hardcoded here (?).
Code: Select all
Command: %WINDIR%\notepad.exe %commander_ini%
The environment variable for to edit the Wcx_ftp.ini is still missing:
TC 6.55 and %Commander_INI%
[REQ] %MAIN_INI% and %FTP_INI% for locating TC's INI files
Posted: 2007-06-07, 21:33 UTC
by StatusQuo
Stance wrote:Put the path to your editor and use "%commander_ini%" as parameter in the command -field. (See Code)
Code: Select all
Command: %WINDIR%\notepad.exe %commander_ini%
Great, thanks. This way it gets as flexible as the menu command should be.
Posted: 2007-06-07, 21:48 UTC
by Sombra
Hi, For edit the wcx_ftp.ini file with your favorite editor:
Code: Select all
[em_ftp_cfg]
Menu=Edit FTP settings...
Cmd=notepad.exe
Param=wcx_ftp.ini
Path=%COMMANDER_INI%\..
Put in Cmd=
<your editor>