10 ms·
Bringing Bash's powerful command line editing to Microsoft Windows' cmd.exe
- slu 14y agoLooks sweet. I currently have to use Windows at the customer I'm working for. I've installed Console which gives tabs and better copy-n-paste on Windows. See http://sourceforge.net/projects/console/ http://sourceforge.net/projects/console/ I'm not sure if clink and Console will work together, but I'll have to try it.
- rbn 14y agoI use console too and it's awesome. I love the tabs and the transparency feature.
- 7D8 14y agoyea, i've been using Console2 for the last year and absolutely love it.
- ot 14y agoConsole2 regularly crashes on my Windows 7, and it looks like it's not actively developed. I'm giving ConEmu a try and it looks awesome! http://code.google.com/p/conemu-maximus5/ http://code.google.com/p/conemu-maximus5/ Scott Hanselman wrote a blog post about it: http://www.hanselman.com/blog/ConEmuTheWindowsTerminalConsolePromptWeveBeenWaitingFor.aspx http://www.hanselman.com/blog/ConEmuTheWindowsTerminalConsol...
- daliusd 14y agoConsole2 looks releases 1-2 releases per yer. Looks quite stable while not active as some other projects. Check dates here: http://sourceforge.net/projects/console/files/console-devel/2.00/ http://sourceforge.net/projects/console/files/console-devel/...
- slu 14y agoI've never had a single crash (of Console2) on my Win7.
- daliusd 14y agoI have tested and clink works with Console. Actually I don't see reason why it shouldn't work with Console. Maybe there might be shortcuts collisions but I have not met yet any.
- alanbyrne 14y agoWhat's wrong with Powershell?
- est 14y agostarts too slow.
- pjmlp 14y agoon my PC it is instantaneous, it is a matter of hardware.
- shortlived 14y agoNo, 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.
- pjmlp 14y agoTry it on a T410, i7 with 8GB of RAM and a SSD, it takes 2s to start.
- shortlived 14y agoit's a SHELL for God's sake! I shouldn't need 8GB and SSD!!!
- archangel_one 14y agoit 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!
- drivebyacct2 14y agoYeah, 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.
- 38leinad 14y agojust use cygwin
- ot 14y agoI feel like cygwin manages to combine the worst of UNIX and the worst of Windows. And the commands that use the cygwin runtime are noticeably slower than the native counterparts. Also, AFAIK there is no 64bit version yet, which for me is a dealbreaker (I often work with files larger than 2GB).
- EvilTerran 14y agoI'm with you there -- I find Cygwin starts slow and unstable, and then seems to rot at an astonishing speed, to the point where it's usually unusable after I've had it installed for a couple of months.
- barrkel 14y agoCygwin doesn't rot. It doesn't automatically update, and nor does it self-configure, so there's nothing to cause the rot. I've never had problems like you describe. The biggest problem - and what I suspect is happening to you - is when you have third-party programs and utilities that interfere with Cygwin, most often by putting an older or newer version of cygwin1.dll on the $PATH (i.e. you may be using Cygwin as part of some other program and not be aware of it). Cygwin uses shared memory; multiple versions of cygwin1.dll disagree on the format of this shared memory, and things go pear-shaped pretty quickly from there. Also some antivirus programs can trip up Cygwin; in its emulation, it sometimes has cause to open, close then open files in quick succession, but AV programs sometimes analyse files when they are opened by programs, and cause bogus timing-dependent sharing errors.
- msluyter 14y agoI love Cygwin, but I have experienced what I would describe as rot. (manifested via errors on fork()). I think that's caused by things changing around it, via windows dll updates, but I don't have a lot of insight into windows' dll handling and whatnot so I don't know for sure. Also pretty sure installing new cygwin packages can cause this. Usually, rebaseall fixes such problems. In any event, I much prefer Cygwin to the alternatives.
- projectileboy 14y agoIs this different from Unix Utils? Every gig I've ever been on where I'm forced to use a Windows box, first thing I do is load the Unix Util exes into some directory and add it to the path. http://unxutils.sourceforge.net/ http://unxutils.sourceforge.net/
- pudquick 14y agoIf you like unixutils, you might like GOW a bit more: https://github.com/bmatzelle/gow/wiki/executables_list https://github.com/bmatzelle/gow/wiki/executables_list https://github.com/bmatzelle/gow/wiki https://github.com/bmatzelle/gow/wiki Kept up to date, every .exe (once installed) is self-contained (no external .DLLs) and portable to just about any Windows box I've run into. No Cygwin or MinGW installation required. Bash is actually available in the list (albeit an older version) if you really wanted "bash on Windows"
- mih 14y agoThanks. I used to use GNUWin32 (http://gnuwin32.sourceforge.net/ http://gnuwin32.sourceforge.net/), but this seems like a good alternative.
- to3m 14y agoThis was my thought too, but I pushed GOW to a lower priority in my to-do list after a comment in a recent thread that publicised it: http://news.ycombinator.com/item?id=4085830 http://news.ycombinator.com/item?id=4085830
- m_rcin 14y agoAre you sure it's kept up to date? The initial github commit has comment "Initial import of the code I developed back in 2006. Nothing has been changed since then.", and nothing has been changed since that commit (with exception of docs, Gow.nsi and gow.vbs files).
- malkia 14y agoThere is also busybox for Windows - https://github.com/pclouds/busybox-w32 https://github.com/pclouds/busybox-w32
- gouranga 14y agoI've switched to powershell ISE on windows (shipped with it) rather than cmd hosted powershell. Does the job!
- omaranto 14y agoIs it worth installing .NET 3.5 to run the ISE? I use Powershell but only have .NET 4 which runs it just fine. I'm a little surprised that ISE requires 3.5.
- gouranga 14y agoIt doesn't make any difference. It required 3.5 as win7 shipped with that framework. You may actually have 3.5 installed already. Check for the following dir: c:\windows\Microsoft.net\framework\v3.5 If it's there you have it already.
- noveltyaccount 14y agoHave you tried the ISE on Win8 yet? It gets some nice upgrades around intellisense.
- gouranga 14y agoNot yet - will fire up my vm later. Thanks for the tip!
- deleted 14y ago[deleted]
- ehosca 14y agoDo yourself a favor, learn PowerShell if you have to work on Windows. http://technet.microsoft.com/library/bb978526.aspx http://technet.microsoft.com/library/bb978526.aspx
- Graphon 14y agoWhile powershell is a valuable and interesting option, the problem with it is that it changes the basic metaphor. For 40 years unix shells and their descendants and derivatives including cmd.exe have used files and text streams as the metaphor for interconnecting processes. Powershell changes that, and it means the output of one command goes to the input of another command as "objects". This can be powerful, but it is also very disorienting. Which means it can be hard to learn to do even basic things in powershell, things that would take only a pipe or two and a couple unxutls programs in cmd.exe. In cmd.exe, easy things are easy and hard things can be really hard. In powershell, hard things are hard (as opposed to "really hard") and easy things are hard.
- gouranga 14y agoI'm not a fan of powershell but I have to use it in my line of work. The only thing that I find sucks is that the pipeline is slow as snails. For example, an svnadmin dump piped to a file which takes 8 mins in cmd.exe takes 14 hours in powershell... Apart from that it's bearable!
- pjmlp 14y agoReally 14hours?! Have you tried to change the way the dump is done?
- gouranga 14y agoWell you can only pipe to file as the output is on stdout. We just ran it through cmd.exe instead. 8 mins is fine - it's a 12Gb repo. I assume it's related to PS converting every line into a system.string.
- malkia 14y agoOr just use Far Manager - http://www.farmanager.com http://www.farmanager.com - it's Midnight Commander, Norton Commander type of program.
- shortlived 14y agoI've watched numerous Russian colleagues use it and it does not look appealing. These same colleagues do not seem to understand the power of a real *nix shell. You end up doing less typing if you really know your shell and how to pipe etc.
- malkia 14y agoYou can run cygwin shell from FAR, or any other shell. Seriously. Think of Far Manager as Midnight Commander, more or less.
- Bjartr 14y agoWhy use this over a cross-compiled version of Bash?