CTRL + C kills entire terminal tab #6850

@oledid commented on GitHub (Mar 13, 2020):

@DHowett-MSFT with scoop, https://scoop.sh, «scoop install pwsh» probably

@oledid commented on GitHub (Mar 13, 2020): @DHowett-MSFT with scoop, https://scoop.sh, «scoop install pwsh» probably

claunia commented

@DHowett-MSFT commented on GitHub (Mar 13, 2020):

This is very similar to https://github.com/PowerShell/PowerShell/issues/11314, but scoop needs to fix it on their end. Same exact problem. I can’t find the bug on their tracker right now, but somebody did file it. 😄

@DHowett-MSFT commented on GitHub (Mar 13, 2020): This is very similar to https://github.com/PowerShell/PowerShell/issues/11314, but scoop needs to fix it on their end. Same exact problem. I can’t find the bug on their tracker right now, but somebody did file it. 😄

claunia commented

@oledid commented on GitHub (Mar 13, 2020):

Thanks!

If other people are reading this, the solution is to change the exe being used, in windows terminal's profiles.json:

"commandline": "C:\\Users\\username\\scoop\\apps\\pwsh\\current\\pwsh.exe",

@oledid commented on GitHub (Mar 13, 2020): Thanks! If other people are reading this, the solution is to change the exe being used, in windows terminal's `profiles.json`: ```json "commandline": "C:\\Users\\username\\scoop\\apps\\pwsh\\current\\pwsh.exe", ```

claunia commented

@jorgensigvardsson commented on GitHub (Mar 17, 2020):

Thanks!

If other people are reading this, the solution is to change the exe being used, in windows terminal's profiles.json:
"commandline": "C:\\Users\\username\\scoop\\apps\\pwsh\\current\\pwsh.exe",

So, I've installed it as a global dotnet tool. How do I solve it? This is causing neural damage... I've become wary of using Ctrl+C. 😖

@jorgensigvardsson commented on GitHub (Mar 17, 2020): > Thanks! > > If other people are reading this, the solution is to change the exe being used, in windows terminal's `profiles.json`: > > ```json > "commandline": "C:\\Users\\username\\scoop\\apps\\pwsh\\current\\pwsh.exe", > ``` So, I've installed it as a global dotnet tool. How do I solve it? This is causing neural damage... I've become wary of using Ctrl+C. :confounded:

claunia commented

@oledid commented on GitHub (Mar 17, 2020):

@jorgensigvardsson I haven't done that, but the problem for the scoop installation was that the pwsh.exe in PATH was a shimmed .exe, which did not work. If I changed to the real .exe, it worked. Maybe the global dotnet tool-installation also has another shim .exe? Check what you have in PATH when you run where.exe pwsh

@oledid commented on GitHub (Mar 17, 2020): @jorgensigvardsson I haven't done that, but the problem for the scoop installation was that the pwsh.exe in PATH was a [shimmed](https://en.wikipedia.org/wiki/Shim_(computing)) .exe, which did not work. If I changed to the real .exe, it worked. Maybe the global dotnet tool-installation also has another shim .exe? Check what you have in PATH when you run `where.exe pwsh`

claunia commented

@oledid commented on GitHub (Mar 17, 2020):

Or locate the installation directory and see if there is another exe there

@oledid commented on GitHub (Mar 17, 2020): Or locate the installation directory and see if there is another exe there

claunia commented

@jorgensigvardsson commented on GitHub (Mar 17, 2020):

@oledid I only find pwsh.exe in my global dotnet directory C:\Users\user\.dotnet\tools. Maybe I should install it as a "real" application as well.

@jorgensigvardsson commented on GitHub (Mar 17, 2020): @oledid I only find `pwsh.exe` in my global dotnet directory `C:\Users\user\.dotnet\tools`. Maybe I should install it as a "real" application as well.

claunia commented

@oledid commented on GitHub (Mar 17, 2020):

@jorgensigvardsson Yeah, maybe. Post it here if you find out :)

@oledid commented on GitHub (Mar 17, 2020): @jorgensigvardsson Yeah, maybe. Post it here if you find out :)

claunia commented

@jorgensigvardsson commented on GitHub (Mar 17, 2020):

@oledid I downloaded the Power Shell 7 distribution for Windows x64, and Ctrl+C now works as expected. I hope my neurons will recover in time. 😀

@jorgensigvardsson commented on GitHub (Mar 17, 2020): @oledid I downloaded the Power Shell 7 distribution for Windows x64, and Ctrl+C now works as expected. I hope my neurons will recover in time. 😀

claunia commented

@jorgensigvardsson commented on GitHub (Mar 17, 2020):

And thank you very much for your help @oledid!

@jorgensigvardsson commented on GitHub (Mar 17, 2020): And thank you very much for your help @oledid!

claunia commented

@oledid commented on GitHub (Mar 17, 2020):

@jorgensigvardsson No prob, the problem made me pretty crazy too :)

@oledid commented on GitHub (Mar 17, 2020): @jorgensigvardsson No prob, the problem made me pretty crazy too :)

claunia commented

@Livven commented on GitHub (Mar 21, 2020):

FWIW this is the scoop issue: https://github.com/lukesampson/scoop/issues/3634 @DHowett-MSFT

@Livven commented on GitHub (Mar 21, 2020): FWIW this is the scoop issue: https://github.com/lukesampson/scoop/issues/3634 @DHowett-MSFT

claunia commented

@CHerSun commented on GitHub (Jul 15, 2020):

Thank you @oledid . Just a small note: when configuring pwsh installed using Scoop in Windows Terminal replace line:
"source": "Windows.Terminal.PowershellCore",
with
"commandline": "%USERPROFILE%\\scoop\\apps\\pwsh\\current\\pwsh.exe",
if you are using default Scoop installation path.

To add icon:
"icon": "%USERPROFILE%\\scoop\\apps\\pwsh\\current\\assets\\StoreLogo.png",

@CHerSun commented on GitHub (Jul 15, 2020): Thank you @oledid . Just a small note: when configuring `pwsh` installed using **Scoop** in Windows Terminal replace line: `"source": "Windows.Terminal.PowershellCore",` with `"commandline": "%USERPROFILE%\\scoop\\apps\\pwsh\\current\\pwsh.exe",` if you are using default Scoop installation path. To add icon: ` "icon": "%USERPROFILE%\\scoop\\apps\\pwsh\\current\\assets\\StoreLogo.png",`

claunia commented

@AndrewSav commented on GitHub (Jan 8, 2022):

Alternatively scoop config shim kiennq seems to also work, after that you need to recreate the shim with scoop update -f pwsh

@AndrewSav commented on GitHub (Jan 8, 2022): Alternatively `scoop config shim kiennq` seems to also work, after that you need to recreate the shim with `scoop update -f pwsh`

claunia commented