When selecting 'Change Settings Files Directly' in the configuration menu,
TC launches Notepad as editor. I want to use my own editor, ED for Windows or Editpad Pro. How can this be done ? Notepad is too limited for realworld use ...
TIA
Change Settings Files Directly
Moderators: Hacker, petermad, Stefan2, white
-
- Junior Member
- Posts: 63
- Joined: 2006-02-06, 08:51 UTC
- Location: antwerp, belgium
Hi, Bob.
This request has been made more than once in the past.
As you can tell from your own experience so far the request has been rejected.
The reason for not changing the internal command "cm_ConfigChangeIniFiles=581 ; Open ini files in notepad" is that notepad.exe is guaranteed to be available on all Windows systems.
A possible workaround is by assigning a button which will launch your favourite editor and which will pass the names of the INI files as commandline arguments:
+ "%COMMANDER_INI%"
+ "%COMMANDER_INI%\..\WCX_FTP.ini"
If you have changed the name of FTP ini-file you will have to change the second argument.
In case you wish to replace Notepad by your favourite editor systemwide you might give NotepadReplacer a try. (I know there are dozens of other NotepadReplacers around as well.)
Oh, by the way, I'd be glad if cm_ConfigChangeIniFiles simply used the editor which I have told T.C. to use when I press F4 or Shift-F4.
So, yes, I support your request and all the old requests to the same effect.
Kind regards,
Karl
This request has been made more than once in the past.
As you can tell from your own experience so far the request has been rejected.
The reason for not changing the internal command "cm_ConfigChangeIniFiles=581 ; Open ini files in notepad" is that notepad.exe is guaranteed to be available on all Windows systems.
A possible workaround is by assigning a button which will launch your favourite editor and which will pass the names of the INI files as commandline arguments:
+ "%COMMANDER_INI%"
+ "%COMMANDER_INI%\..\WCX_FTP.ini"
If you have changed the name of FTP ini-file you will have to change the second argument.
In case you wish to replace Notepad by your favourite editor systemwide you might give NotepadReplacer a try. (I know there are dozens of other NotepadReplacers around as well.)
Oh, by the way, I'd be glad if cm_ConfigChangeIniFiles simply used the editor which I have told T.C. to use when I press F4 or Shift-F4.
So, yes, I support your request and all the old requests to the same effect.
Kind regards,
Karl
-
- Junior Member
- Posts: 63
- Joined: 2006-02-06, 08:51 UTC
- Location: antwerp, belgium
Is this rejection of legitimate requests not a bit shortsighted ? Nothing can be more simple than adding a test 'is notepad.exe there or not' and then communicate the result to the user. Plain and simple. And yes, it seems so evident to use the defined internal editor. How hard can it be ...
However, thanks for the effort.
However, thanks for the effort.
Hi, Bob.
Christian's argument against changing the behaviour of "cm_ConfigChangeIniFiles" (Change Settings Files Directly) is not that it where hard to implement.
The reason as I tried to explain is that a user might configure an inappropriate programme as his/her editor thus making "cm_ConfigChangeIniFiles" (Change Settings Files Directly) unusable.
My point of view:
If I want to shoot myself in the foot, I will find a way of achieving my goal. No real need to prevent me from doing so.
Even if I manage to make "cm_ConfigChangeIniFiles" (Change Settings Files Directly) unusable by telling T.C. to launch an inappropriate programme as my editor, even then I am still able to double click wincmd.ini and wcx_ftp.ini manually in Explorer which will launch the systemwide editor (presumably notepad.exe). So there will always be a chance of undoing any misconfiguration.
In the worst case I have to rename my wincmd.ini file to wincmd.bad.ini and relaunch T.C. thus restoring all its default parameters and the ability to "change settings files directly" by invoking notepad.exe.
Kind regards,
Karl
Christian's argument against changing the behaviour of "cm_ConfigChangeIniFiles" (Change Settings Files Directly) is not that it where hard to implement.
The reason as I tried to explain is that a user might configure an inappropriate programme as his/her editor thus making "cm_ConfigChangeIniFiles" (Change Settings Files Directly) unusable.
My point of view:
If I want to shoot myself in the foot, I will find a way of achieving my goal. No real need to prevent me from doing so.
Even if I manage to make "cm_ConfigChangeIniFiles" (Change Settings Files Directly) unusable by telling T.C. to launch an inappropriate programme as my editor, even then I am still able to double click wincmd.ini and wcx_ftp.ini manually in Explorer which will launch the systemwide editor (presumably notepad.exe). So there will always be a chance of undoing any misconfiguration.
In the worst case I have to rename my wincmd.ini file to wincmd.bad.ini and relaunch T.C. thus restoring all its default parameters and the ability to "change settings files directly" by invoking notepad.exe.
Kind regards,
Karl
- Balderstrom
- Power Member
- Posts: 2148
- Joined: 2005-10-11, 10:10 UTC