Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

Post by rocqua » Sat, Nov 19, 2016, 12:25 AM UTC

brazzledazzle wrote: post #203

Diti wrote: post #35

Something 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

I don't think this is a good default for posh on nix platforms but I would argue that it's a good thing on Windows. The output of PowerShell ls is an object with typed properties and methods that you can interact with in a much richer way. Not to mention user experience. Adding these aliases made moving back-and-forth between nix and Windows much less jarring for me. They also really helped drive home the difference…

Post by eridius » Sat, Nov 19, 2016, 12:40 AM UTC

hota_mazi wrote: post #289

thebspatrol wrote: post #281

Earlier quoted context omitted.

CMD + { and CMD + }

Thanks but... yuck. Any way I can remap these? Cmd- is a pretty standard way to jump to tabs (and arguably, Ctrl-tab as well).

Post by brownbat » Sat, Nov 19, 2016, 12:40 AM UTC

kevin_thibedeau wrote: post #298

brownbat wrote: post #254

Earlier quoted context omitted.

> good Unicode support from the very beginning I once started a Chinese character flash card program in Python on Windows. The yak shaving was unbelievable. I never got a working version, but I learned a lot about code pages, and why "building a console from scratch" is not actually the right answer to "I want to be able to test a toy program I'm making before it's finished."

Tkinter would have given you a basic Unicode capable GUI without the hassles of the console.

Post by to3m » Sat, Nov 19, 2016, 12:56 AM UTC

to3m wrote: post #183

herbst wrote: post #75

Earlier quoted context omitted.

That is actually pretty interesting, thanks for linking! I still dont understand how this was not "fixed" years ago, sure some config windows have fixed widths because it makes sense, but something as a terminal obviously needs the ability to grow (or shrink), especially after they introduced sticky windows and people actually used "tiling"

The idea that the console screen is an MxN matrix is pretty embedded in the API... it's not a MDA display adapter metaphor, not a Unix-style typewriter. I'm guessing they just felt they had bigger fish to fry. (Everybody I know that uses the console window a lot has always just set the window to 120x9999 or 160x9999 or whatever and forgotten about it. It's one of those things that's obviously kind of lame, but after…

Post by mattmanser » Sat, Nov 19, 2016, 1:36 AM UTC

UnoriginalGuy wrote: post #264

WayneBro wrote: post #209

Windows fan here. I hate PowerShell and I'd much rather have Bash built into Windows. Things I hate about PowerShell: - You can't even run your own scripts without performing the Set-ExecutionPolicy ceremony first or signing your scripts. - It's way too verbose. - It's a strange bird that next to nobody uses, so there's zero motivation to learn it. - It's not "old reliable". You can't depend on it working due to the…

I'm going to address each bullet: - Set-ExecutionPolicy can be set with a single click from the "For Developer Settings." Just scroll down and hit Apply three times and your machine has sane developer defaults (inc. ExecutionPolicy). - The verbosity means that you can "guess" PS commands. Each PS command is a set layout with an action word (e.g. Add, Clear, Get, Write, etc) and then target (e.g. Set-Alias, Set-Date,…