solved [TC 11.00b10] cm_Edit does not work with parameters in Command field

[petermad]

05.07.23 Added: cm_Edit with parameters: Option to open the file with associated program instead of editor, either with or without using internal associations (32/64)

This button works as expected:

Code: Select all

TOTALCMD#BAR#DATA
cm_Edit
/CTN="myfile.txt"L3
wcmicons.dll,28
Create and edit myfile.txt

Wheras this button doe not:

Code: Select all

TOTALCMD#BAR#DATA
cm_Edit /CTN="myfile.txt"L3

wcmicons.dll,28
Create and edit myfile.txt

It gives an error mesage from the default editor with a text like this "The syntax in the file name, the folder or the drive name is wrong"

[ghisler(Author)]

Confirmed, I was calling it with the wrong parameter.

[petermad]

06.07.23 Fixed: cm_Edit didn't work with parameters directly after cm_Edit (e.g. on a button) instead of in the parameters field (32/64)

Confirmed fixed in TC 11.00rc1

[petermad]

I was too hasty.

cm_Edit still does not work with /N="%|COMMANDER_INI|" in the command field, only in the Parameters field.

cm_Edit /N="%|COMMANDER_INI|" does work OK in TC's command line.

cm_Edit /N="%|COMMANDER_PATH|\wincmd.ini" does not work either in command field

[ghisler(Author)]

Since it's the command field, you would have to use %COMMANDER_INI% and not %|COMMANDER_PATH|. However, this isn't currently supported in cm_Edit.

[petermad]

I tried %COMMANDER_INI% and it didn't works (as you also write), so I thought ought to be supportede in the command field, since it is supported in the command line.

this isn't currently supported in cm_Edit.

Any chance that it will be supported in the future??

[ghisler(Author)]

Yes, it's on my to do list.

[petermad]

13.07.23 Fixed: cm_Edit: Support environment variables in command field, in option N="name(s)" (32/64)

Confirmed fixed in TC 11.00rc2