[TC 11.50b7] Environment variables are not expanded after returning from pseudo-variable $CLIP*

[Fla$her]

1. Select %COMMANDER_PATH% and copy to clipboard.
2. Execute from the command line, button, etc. some of this:

• cd %$CLIPBOARD%
• cd %$CLIPNAME1%

• Code: Select all

  TOTALCMD#BAR#DATA
  cd
  ?%|$CLIPBOARD0| %|$CLIPNAME1|
  wcmicon2.dll,45
  Check the variables

The result is negative.

[AntonyD]

.

[ghisler(Author)]

%$CLIPBOARD*% and %$CLIPNAME*% insert data from the clipboard as is. No environment variable substitution is done for the data from the clipboard. This is not a bug, other environment variables aren't resolved recursively either, this could lead to infinite loops, e.g. when the clipboard already contains %$CLIPBOARD%. That would be easy to detect, but it can be cyclic like this:
%$CLIPBOARD% -> clipboard contains %SOMEVAR% -> SOMEVAR contains %$CLIPBOARD%

Moderator message from: ghisler(Author) » 2024-11-25, 09:34 UTC

Moved to will not be changed.

[Fla$her]

but it can be cyclic like this:

It's amazing to read! Why don't different scripts do this, but TC will suddenly do it?
Why do cyclic operations here, if you only expand the variable only once?
Is it possible to simply not use cyclic operations?