solved [TC 11.00b1] parameters for cm_copy not working from command line

[petermad]

The new parameters for CM_COPY, CM_RENMOV and CM_CREATESHORTCUT does not work when used in TC's command line.

[ghisler(Author)]

This is indeed not supported for any command with more complex parameters.

[petermad]

2ghisler(Author)
OK.

Is it on purpose that those parameters are case sensitive (only works in uppercase)?

[AntonyD]

Topic named '[TC 11.00b1]....' but exists in 'TC10.x bug reports (English)' sub-forum?
Maybe we need to move it?

[petermad]

Topic named '[TC 11.00b1]....' but exists in 'TC10.x bug reports (English)' sub-forum?

That is not correct.

EDIT - I have been informed that it was correct, but that the tr´thread was silently moved by moerator - sorry.

[ghisler(Author)]

Is it on purpose that those parameters are case sensitive (only works in uppercase)?

Yes, because otherwise you couldn't launch a program with that name any more (except by explicitly adding .exe or so).

[petermad]

Yes, because otherwise you couldn't launch a program with that name any more (except by explicitly adding .exe or so).

I was referring to the cm_Copy parameters /PVB1B2SHAGTW why do they have to be in uppercase?

[ghisler(Author)]

The parameters in the button bar like %N and %n are also case sensitive.
Would it be better to make the cm_Copy parameters case insentive?

[petermad]

The parameters in the button bar like %N and %n are also case sensitive

That makes sense, because they have differnent meanings.

Would it be better to make the cm_Copy parameters case insentive?

I think so. The only two other command that use alphanumeric paramers OPENATTRIBUTES and ZIPFROMLIST use case insensitive parameters.

[ghisler(Author)]

OK, it's easy to add.

[petermad]

08.05.23 Fixed: cm_copy: The parameters are now case insensitive (lowercase also supported) (32/64)

Confirmed fixed in TC 11.00b2

I would still have liked it to also work from command line.