Repository navigation
Create pwsh as a shorter name for calling powershell.exe #4214
Description
Activity
I would like a short alias too, but this is why we didn't get go with
poshwhen we first went out (we talked about it at length). Appears to be still an up-to-date package too.Open to other suggestions, but most of the obvious *sh ones have been taken. After the only wget/curl alias thing, I'd really like to avoid colliding with other packages out there, even if they're less common.
Reacted by Ionuț Jula, Retia and Andrew JankeI'm not too crazy about this whole idea but how about
pwsh?Reacted by Michael Klement, Julius and jax999I've never been keen on posh as a shortening of powershell. pwsh seems better but a quick internet search raises some possible issues. if we're going to do this I'd suggest as short as possible so what about just ps?
OK - forget that - I just realised ps is an alias for get-process. that would be too confusing
Reacted by Joey Aiello, Ionuț Jula and Andy JordanI'm getting strong deja vu right now. 😉
Reacted by Keith HillI appreciate PowerShell's readability (when not using aliases) so running
powershellworks fine for me.Reacted by Felix Becker, Rafal Klys, i-give-up and Justin Kingpsis an existing command on Linux as well.Some other ideas are:
pscmd,psc,monad,psh,pshellThere is definitely diminishing returns with these names though on whether they really save anything or just add unnecessary confusion if they are even available.
CoreSh,pcs,psc😄 S#, P#
125 remaining items
Mark Kraus (@markekraus) has a nice blog post that captures the what and whys:
https://get-powershellblog.blogspot.sg/2017/10/why-pwsh-was-chosen-for-powershell-core.html
Reacted by Mark Kraus, Sander Saares, Werner Mairl, Joel Bennett, Ryan Spletzer, i-give-up and Andrius KToday I saw the first usage of
pwshon SO here although I doubt that the person knows about this thread...- added a commit that references this issue
on Dec 18, 2017 Can we get an official ruling on the pronunciation of
pwsh? The PNG spec includes a pronunciation in its Section 1. May as well provide one for PowerShell; don't want another SCSI "scuzzy"/"sexy" situation.Looks like "poosh" to me.
Andrew Janke (@apjanke) the generally accepted pronunciation of
pwshisposhReacted by Kagami Sascha RosylightWorks for me. Thanks for the official confirmation!
Why was this never fixed? It is still "pwsh" in Mac/Linux and "powershell" in Windows - so broken
Why was this never fixed? It is still "pwsh" in Mac/Linux and "powershell" in Windows - so broken
Maybe because you haven't installed PowerShell Core?
Cloudmersive (@Cloudmersive) Kagami Sascha Rosylight (@saschanaz) is right. Here's why. There are two different implementations of PowerShell. The original "Windows PowerShell" that has shipped with Windows since Windows 7. This is powershell.exe and does not run on anything but Windows. It is built on the desktop version of the .NET Framework (Windows only).
Then there is the cross-platform version of PowerShell built on .NET Core that started life as "PowerShell Core" but has recently been shortened to just "PowerShell". It does not come with Windows atm. But it runs on Linux, macOS and Windows. You have to install it separately. This is pwsh.exe. On Windows, you will have both powershell.exe and pwsh.exe (if you install it) and they do behave a bit differently due to differences between .NET Framework and .NET Core. There are folks still using powershell.exe where the move to pwsh.exe would break their scripts. So we need both names.
Reacted by Kagami Sascha Rosylight and Andrew JankeCan someone teach the bot to lock closed posts after a few months so we don't all get pinged when someone zombies them?
Reacted by Kagami Sascha Rosylight, Rain Sallow (/u/ta11ow), Ilya and Thomas LeeWhy was this never fixed? It is still "pwsh" in Mac/Linux and "powershell" in Windows - so broken
Well - it was never broken. PWSH.EXE and POWERSHELL.EXE are two quite different products and are not totally compatible. There are things you can do on one but not the other.
TL;DR: nothing is broken.
And I agree with Joel Bennett (@Jaykul)!
Can someone teach the bot to lock closed posts after a few months so we don't all get pinged when someone zombies them?
I'll lock this issue. Locking all old issues is something that's been discussed before, but we have a few active old issues and personally it seems a bit heavy handed to me. Feel free to raise it in a separate discussion, like the community call or similar.
- locked and limited conversation to collaborators
on Jun 16, 2021 We have GitHub Discussions now.
The muscle memory from switching cmd to powershell is a pain. It is made worse by the fact that it is much longer than typing out cmd or bash. Even with Windows Search in Start, it often picks up the ISE if you have been using it awhile, so typing out the full name is often needed.
A better name would be posh.exe or other valid extension. It is as long as bash and just one character longer than cmd. Posh has been the accepted abbreviation in the community for all things PowerShell so there is some familiarity there. I don't believe there are any conflicts with other apps that this would cause, but that would need some digging.
This could be achieved in two ways.
The former maintains backwards compatibility and allows the user to choose between posh or powershell.exe. Existing scripts not impacted.
The latter could help give more freedom to issues like #4199 and other POSIX proposals to how the shell is started. However, it is a breaking change and would need to be reviewed for the impact and the branding implication.
I think making an official posh shortcut is the best option with minimal impact. New documentation could give preference to posh as the way to enter PowerShell.