Bringing Bash's powerful command line editing to Microsoft Windows' cmd.exe

Re:Bringing Bash's powerful command line editing to Microsof... by pjmlp on Sunday July 01, 2012 @02:04PM (#4185574)

on my PC it is instantaneous, it is a matter of hardware.

[ Parent | on HN ]

Re:Bringing Bash's powerful command line editing to Microsof... by shortlived on Sunday July 01, 2012 @06:06PM (#4186310)

No, it's not. I have a TI6x laptop, 4gb of RAM, plenty o' CPU and with no other user-space programs running, it still takes FOREVER to start. I feel like i'm launching Eclipse or something.

[ Parent | on HN ]

Re:Bringing Bash's powerful command line editing to Microsof... by pjmlp on Monday July 02, 2012 @12:10PM (#4189424)

Try it on a T410, i7 with 8GB of RAM and a SSD, it takes 2s to start.

[ Parent | on HN ]

Re:Bringing Bash's powerful command line editing to Microsof... by shortlived on Tuesday July 03, 2012 @02:23PM (#4195427)

it's a SHELL for God's sake! I shouldn't need 8GB and SSD!!!

[ Parent | on HN ]

Re:Bringing Bash's powerful command line editing to Microsof... by archangel_one on Sunday July 01, 2012 @06:51PM (#4186411)

it is not a matter of hardware. On my ex-work desktop (2.8GHz quad core, so fairly quick) it used to take a good 5-10 seconds to be ready from a cold start. Yes, subsequent starts were faster, but it's a flipping shell, it shouldn't need hefty hardware to start quickly!

[ Parent | on HN ]

Re:Bringing Bash's powerful command line editing to Microsof... by EnderMB on Monday July 02, 2012 @06:10AM (#4188189)

Absolutely. Even on my work machine (2.2GhZ, 4GB RAM) it loads within a second.

[ Parent | on HN ]

Re:Bringing Bash's powerful command line editing to Microsof... by drivebyacct2 on Monday July 02, 2012 @12:37AM (#4187343)

Yeah, I can also handily disagree with this. My test machine has a 6 month old CPU and 6GB of RAM. I can reboot, wait 5 minutes and try to launch PowerShell and still be looking at a 5-15 second wait.

[ Parent | on HN ]