[9.10x64b1] F7, environment variables not expanded

wanderer · Post by *wanderer » 2017-09-20, 18:19 UTC

F7. I tried to create folder:

%TEMP%\TC\Log

but TC, instead of expanding %TEMP% to C:\Users\<User>\AppData\Local\Temp, it just created a folder %TEMP%\TC\Log in the current folder.

sqa_wizard · Post by *sqa_wizard » 2017-09-20, 20:40 UTC

Well, yes that it the way it works - straight forward.
How else do you create a folder with name "%TEMP%" ?

wanderer · Post by *wanderer » 2017-09-20, 20:45 UTC

sqa_wizard wrote:Well, yes that it the way it works - straight forward.
How else do you create a folder with name "%TEMP%" ?

Hmmm. A better question might be "how do you "cd" into it".

I'm talking about a classic command-prompt "cd" of course.

Dalai · Post by *Dalai » 2017-09-20, 23:23 UTC

I think this is intentional, or at least it's not a bug because TC 8.52a behaves the same way.

Regards
Dalai

wanderer · Post by *wanderer » 2017-09-21, 06:15 UTC

Dalai wrote:I think this is intentional, or at least it's not a bug because TC 8.52a behaves the same way.

Yes, it seems so. IMO it would be nice if a simple checkbox existed somewhere left of the "OK" button, to "expand environment variables".

Lefteous · Post by *Lefteous » 2017-09-21, 06:27 UTC

Hmmm. A better question might be "how do you "cd" into it". Smile

I'm talking about a classic command-prompt "cd" of course.

CD works fine here for these kind of paths.

wanderer · Post by *wanderer » 2017-09-21, 06:33 UTC

Lefteous wrote:CD works fine here for these kind of paths.

Yes, in Powershell. The classic command prompt just goes to the TEMP folder.

Lefteous · Post by *Lefteous » 2017-09-21, 06:37 UTC

Yes, in Powershell. The classic command prompt just goes to the TEMP folder.

I talked about the command-line in TC.

wanderer · Post by *wanderer » 2017-09-21, 06:49 UTC

Lefteous wrote:
Yes, in Powershell. The classic command prompt just goes to the TEMP folder.
I talked about the command-line in TC.

Nope. Here it just goes to TEMP folder. Maybe it's an O/S thing or a matter of TC configuration?

Post by *ghisler(Author) » 2017-09-21, 09:55 UTC

Indeed environment variables cannot currently be used in F7, Shift+F4 etc. I could allow them when using placeholders - either just when prefix < is there, e.g.
<%TEMP%
or in form
<[%temp%]

What do you think?

wanderer · Post by *wanderer » 2017-09-21, 10:14 UTC

ghisler(Author) wrote:What do you think?

Well, it's a nice solution because the user can select which of the variables he wishes to expand, but with this solution you add an extra thing the user has to remember. If you can also add an on-the-screen hint in the dialog (a label with "use < to expand variables")...

Post by *ghisler(Author) » 2017-09-21, 10:46 UTC

I could add a sample like [%temp%] to the + button list.

wanderer · Post by *wanderer » 2017-09-21, 10:49 UTC

ghisler(Author) wrote:I could add a sample like [%temp%] to the + button list.

Yup. That would also not require a translation, right?

sqa_wizard · Post by *sqa_wizard » 2017-09-21, 21:22 UTC

I could add a sample like [%temp%] to the + button list.

Function is getting better and better .. I like it
Support++

Post by *ghisler(Author) » 2017-09-22, 10:14 UTC

OK, [%variable%] added to multi-rename tool, F7 and Shift+F4. Also supports pseudo environment variables in the form [%$variable%], and text range from a variable like [%variable%1-5].