Btw did anyone noticed that in windows 10 you can resize cmd.exe to more than 80 characters width! When I first saw it I almost cried.
Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
131–140 of 350 posts
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#132Something that irks me is how PowerShell’s default aliases take precedence over binaries in the PATH. To be able to use the GNU utils, you have to put this in your profile.ps1 : Remove-Item Alias:cat Remove-Item Alias:cp Remove-Item Alias:curl Remove-Item Alias:echo Remove-Item Alias:ls Remove-Item Alias:man Remove-Item Alias:mv Remove-Item Alias:pwd Remove-Item Alias:rm Remove-Item Alias:wget
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#133So basically instead of doing dir C:\ I have to learn to type List-Directory-With-Files Drive=C Folder=/ (made up example, but you get the point)
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#134Btw did anyone noticed that in windows 10 you can resize cmd.exe to more than 80 characters width! When I first saw it I almost cried.
Also MS should really improve the inbuilt apps to do this stuff.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#135Btw did anyone noticed that in windows 10 you can resize cmd.exe to more than 80 characters width! When I first saw it I almost cried.
IIRC you could resize the standard cmd console easily, just type "mode 160" (or whatever width you want). I don't have a Windows installation around to check it, but maybe someone can confirm?
Display mode: MODE CON[:] [COLS=c] [LINES=n]
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#136Earlier quoted context omitted.
Well, the nice thing in PowerShell is that you have explicit control over "stop parsing here and just pass the rest to the application verbatim" with --%. Solves a lot of quoting nightmares.
That's indeed nice. I wonder if there is something like that for ZSH.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#137Earlier quoted context omitted.
How is that any different from Linux distributions camping their default shell? Like back when debian changed their default shell to dash I don't remember anyone saying you should stay away from debian, even though it broke a lot of existing scripts.
Did you have a choice to upgrade? Could you reinstall the old version of you wanted? Windows has stripped that power from users.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#138> As a result, PowerShell officially replaces the Command Prompt in the Win + X menu, so when you right-click the Start menu, you’ll only be allowed to launch the more powerful app.
This is an older change - I have this behavior in 10.0.14393.0 (ie, current stable).
cmd launching posh is new though.
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#139> Starting with Windows 10 build 14971, Microsoft is trying to make PowerShell the main command shell in the operating system. > As a result, PowerShell officially replaces the Command Prompt in the Win + X menu, so when you right-click the Start menu, you’ll only be allowed to launch the more powerful app. This is an older change - I have this behavior in 10.0.14393.0 (ie, current stable). cmd launching posh is new…
Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
#140How does PS compare to installing cygwyn and using bash ? (from a Linux user perspective) does it support grep, find, ls, PS, pipes, etc?