Replies: 2 comments 1 reply
-
|
To configure an alias in a similar way to Windows PowerShell, use: Set-Alias rm Remove-ItemPowerShell alias resolution takes precedence over native commands, so once you define You can then make this persistent across sessions by adding the command to your PowerShell profile. |
Beta Was this translation helpful? Give feedback.
-
|
PowerShell on Linux can't be the same as when used on Windows. You always have to remember that it's a completely different OS, be aware of the applications that cause the shell to crash, know what won't work, and be aware of what's unavailable. It's a wonderful scripting language, but there are nuances. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When I choose to use Powershell on Linux or MacOS, I want the experience to be as similar to that on Windows as possible, starting with command-line golf operations. For my usage scenarios, I really don't care about the edge-cases. I want "rm -rec -for" to work whatever platform I'm on.
One reason for this is that I need myself and my users to be comfortable shelling with PowerShell in order to increase onboarding to people who [edit] would potentially write actual formal Powershell scripts.
Despite 90% of our users being on Mac, 52% of our script contributions continue to be bash/zsh from Mac/Linux users, 45% powershell from our Windows users, and only 3% powershell from Mac users.
Is there some preferred/well-documented/ideal way to turn off the native shell-command surfacing on lin/mac? Is there a switch or setting somewhere that re-enables the aliases we had back in 6.x or 7.x whatever it was?
Beta Was this translation helpful? Give feedback.
All reactions