Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

news.softpedia.com

Post reply on HN
Print view View original

271–280 of 350 posts

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#271

Post by zlynx »

ryao wrote: post #199
EE84M3i wrote: post #157

Earlier quoted context omitted.

I've only ever really noticed with 'time' and 'echo'

I have noticed this with echo too. In specific, the bash echo built in does not drop support for -n and -e when bash is forced into standards compliance mode as /bin/sh. That causes breakage on systems that use more strictly compliant shells when code was written against bash as sh under the assumption that either -n or -e work. I spotted a regression in Linus' tree a while back where this very thing happened in the…

If it is still an issue you want to fix, you may need to resend the patch periodically. It doesn't look like you got any response at all.

LKML gets hundreds of messages every day. When I used to read it I had a set of search filters to prioritize it. Anything I didn't get to I simply marked Read. There's no way to catch everything on there.

Maybe get it passed through by someone who is in Linus's email filters.

Although it's been a year and you probably don't care anymore. :)

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#273

Post by zlynx »

tonyplee wrote: post #198
TorKlingberg wrote: post #104

Earlier quoted context omitted.

Meanwhile, Gnome Terminal has been taking away the tabs...

Did they, why? I have switch to xfce4-terminal for a while in all my system....

They didn't take away terminal tabs.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#274

Post by WayneBro »

treebeard901 wrote: post #260
WayneBro wrote: post #227

Earlier quoted context omitted.

It's not widely used in the Windows world from what I can see. Walk into any office and ask an IT guy to run "ipconfig". They'll open up cmd.exe without even thinking about it. I read a lot of programming tutorials. Nobody ever reference PowerShell in them. They always instruct people to open cmd. Do you have any evidence to the contrary?

Someone else posted the evidence below. In an attempt to understand and empathize with people who do not share my opinions, I looked back through some of your post history and you said this 5 days ago: "It's never been clear to me why anyone would want to use a completely opaque and undiscoverable interface such as a commandline over a nice GUI for anything. You didn't have to read anything or search around in order…

That's a good point - almost everywhere I go as a consultant...their IT people use the GUI to manage things and not PowerShell.

Most places that I've seen automate things with a .NET program whether it's a service, a console app run via Task Scheduler, an SSIS package and in a few cases - a desktop app.

EDIT: I'm a programmer and not a sysadmin except for on my own network where I do prefer "the easy way" as opposed to the way where you have to do rote memorization to perform simple tasks. If I automate anything, it's also done with .NET or Node.js because I like the tools better and my stuff runs everywhere without performing any ceremonies. I do visit a lot of client sites though and I work with client sysadmins regularly. I'm on the East coast and I work in the NY/NJ/PA area. Also the reason I like bash better is because if I have to memorize anything (and I do, for Linux work)...I'd rather have it be something terse.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#275

Post by krylon »

yitchelle wrote: post #117
krylon wrote: post #40

Earlier quoted context omitted.

My work laptop still runs Windows 7 - and will for the foreseeable future - but that is one of the things that make me curious about Windows 10. It is, of course, easy to ridicule Microsoft for how long it took them to change this, but I think better late than never. (On older versions of Windows, ConEmu[1] does that, too, but it's third-party software, of course. It also supports tabs!) [1] https://conemu.github.io/

Since conemu is mentioned, I'll chimed in with cmder[1]. It builds ontop of conemu and has git-for-windows integrated as well. [1] - http://cmder.net/

Thank you very much! I'll give that a try!

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#277

Post by hota_mazi »

nneonneo wrote: post #166
nailer wrote: post #134

Earlier quoted context omitted.

Most Windows terminal people use ConEmu rather than the inbuilt terminal apps - it's like iTerm2 vs Terminal.app on MacOS. ConEmu adds Unix style cut and paste, tabs, etc. Add openssh, PSReadLine and PSCX and you've got a proper terminal setup. Also MS should really improve the inbuilt apps to do this stuff.

I've used iTerm and Terminal on Mac, and the default Windows Terminal (conhost), PuTTY sand MinTTY on Windows. Terminal.app is much, much better than conhost, even after the Windows 10 update. It's fast, supports a ton of thoughtful features (such as customizable title bars via extended ANSI codes, real line wrapping during resize, good Unicode support from the very beginning, etc.). With Terminal.app I can be quite…

What drove me away from Terminal.app was the fact that I can't use command-1/2/3 to switch tabs. Ctrl-tab doesn't work either.

Did I miss something?

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#278

Post by [deleted] »

nneonneo wrote: post #166
nailer wrote: post #134

Earlier quoted context omitted.

Most Windows terminal people use ConEmu rather than the inbuilt terminal apps - it's like iTerm2 vs Terminal.app on MacOS. ConEmu adds Unix style cut and paste, tabs, etc. Add openssh, PSReadLine and PSCX and you've got a proper terminal setup. Also MS should really improve the inbuilt apps to do this stuff.

I've used iTerm and Terminal on Mac, and the default Windows Terminal (conhost), PuTTY sand MinTTY on Windows. Terminal.app is much, much better than conhost, even after the Windows 10 update. It's fast, supports a ton of thoughtful features (such as customizable title bars via extended ANSI codes, real line wrapping during resize, good Unicode support from the very beginning, etc.). With Terminal.app I can be quite…

[deleted]

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#279

Post by keithnz »

scraft wrote: post #144
nailer wrote: post #134

Earlier quoted context omitted.

Most Windows terminal people use ConEmu rather than the inbuilt terminal apps - it's like iTerm2 vs Terminal.app on MacOS. ConEmu adds Unix style cut and paste, tabs, etc. Add openssh, PSReadLine and PSCX and you've got a proper terminal setup. Also MS should really improve the inbuilt apps to do this stuff.

Whilst I am glad to hear about ConEmu; I have to disagree, I use windows cmd.exe very regularly, and know lots of other people that do, and I have never used ConEmu before! I might give it a try now I know about it.

con emu makes the linix subsystem shell a lot nicer too, in fact has an inbuilt ubuntu theme that makes most colors sane

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#280

Post by Diti »

nailer wrote: post #132
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

That's a bad idea - the inbuilt 'ls' (aka get-childitem - it also works on registry paths) will output real file objects, with properties you can access with 'select' and 'forEach' etc, whereas the GNU tool will output text you'll have to scrape.

I would use `Get-ChildItem` directly in that case. When I use `ls`, I expect it to be POSIX `ls`.
Post reply on HN