-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Launching Files from PowerShell prevents entering additional commands #3652
Comments
As a workaround, launching with 'start' works well start files |
Is this still an issue? |
Yes |
I reproduced your action and whether I write "files" or "start files" it opens with version 2.4.80 |
I looked into this some more, and it seems it's not an issue exclusive to Files - I can reproduce this on many packaged apps made with a variety of frameworks and languages. I'm still not clear on what exactly is causing this. |
I found a PowerShell issue on this. |
As a side effect of Leave app running, if Files is launched from Powershell while it is in the background, the prompt returns immediately. |
Considering this issue is with the platform, and the fact that the issue doesn't occur when Files is open in the background, I think we no longer need to track this issue. For further updates, we suggest subscribing to the issue on the PowerShell repo PowerShell/PowerShell#9970. |
Describe the bug
run files in powershell terminal,the terminal is fixed and could do nothing before close the window.
To Reproduce
call files through pwsh(cmd no simailar problem)
Expected behavior
terminal open the window,and ready to my next input
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
when i choose to run with"start-process files",it works as i wished.
another uwp app works so,and the developer asked me to run it with start-process,
i think it's a tiny issue and easy to fix(unforturnly,i know lettle about uwp app develop,otherwise i will fix it myself)
The text was updated successfully, but these errors were encountered: