Lex Li
Lex Li
https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-9-release/ There is no such argument from Windows Terminal to open a file, so currently what you wanted cannot be implemented.
`HOMEDRIVE` can be a bad option, as examples like [this](https://itectec.com/superuser/overriding-homedrive-and-homepath-as-a-windows-7-user/) show.
Similar to #31
It is intentional to require administrator permissions, as one of the Windows Terminal folder is locked down.
The function `GetProgramFilesFolder` accesses the `WindowsApps` folder, https://github.com/lextm/windowsterminal-shell/blob/master/install.ps1#L150 That folder can only be read by administrators. It is possible to modify the install script to skip that folder, but a...
@p2r2 that requires a very complex mechanism, splitting the install steps to two parts (script files) so that they can be run under two accounts. While I fully understand that...
More investigation is needed before this item can be worked on, 1. Cannot find `Microsoft.WindowsTerminal(Preview)_8wekyb3d8bbwe\wt.exe` on my machine. It seems to be `$Env:LOCALAPPDATA\Microsoft\WindowsApps\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\wt.exe`. 2. On my machine `$Env:LOCALAPPDATA\Microsoft\WindowsApps\wt.exe` is associated...
When did you first execute `install.ps1`? Due to some breaking changes, you might need to run `uninstall.old.ps1`. https://github.com/lextm/windowsterminal-shell/blob/master/uninstall.old.ps1
This is intended as the registry keys go to the account that runs the script only, not all accounts on the machine.
Have no idea how this can be achieved yet.