Support environment variables in shortcuts

[clackwell]

What feature or improvement do you think would benefit Files?

In Windows shortcuts I can use, for example, "%USERPROFILE%" in the shortcut fields "Target:" and "Start in:"

(The shortcut editor goes above and beyond, and even offers completion from the path specified. This feels like it goes too far. I am an advanced user by editing the shortcut and using environment variables in it, I can copy and paste a path just fine. No need to waste time with corner-case hyper-convenience like this.)

But when executing such a shortcut via double click in Files one can see that the process gets launched with the environment specification as is, instead of evaluated. From Process Explorer:

The top entry is when launched from File Explorer.

The bottom entry is when launched from Files. Note the command line, which for the bottom entry still contains the environment variable placeholder.

Requirements

• This proposal will accomplish X
• This proposal will accomplish Y
• This proposal will accomplish Z

Files Version

3.1.1

Windows Version

Windows 11, 23H2

Comments

Unrelated, but the "Windows Version" entry in the Feature Request form mentions "[...] access it from Settings -> About -> Copy -> Windows version", but in Windows 11 it is "[...] access it from Settings -> System -> About -> Copy -> Windows version" instead.

And even then there is no such succinct information as implied by the microcopy in the field:

Instead I see this:

What to provide in such a case?

[yaira2]

Thanks for the report, this definitely looks like a bug. Can you open a separate issue using the bug template? Worst case we can just edit this issue but a separate issue would be best.

And even then there is no such succinct information as implied by the microcopy in the field:

Settings refers to the settings in Files