71–80 of 96 posts
Or just use Far Manager - http://www.farmanager.com - it's Midnight Commander, Norton Commander type of program.
I'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.
Think of Far Manager as Midnight Commander, more or less.
Earlier quoted context omitted.
starts too slow.
on my PC it is instantaneous, it is a matter of hardware.
Looks 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/ I'm not sure if clink and Console will work together, but I'll have to try it.
Looks 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/ I'm not sure if clink and Console will work together, but I'll have to try it.
Console2 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/ Scott Hanselman wrote a blog post about it: http://www.hanselman.com/blog/ConEmuTheWindowsTerminalConsol...
Earlier quoted context omitted.
I do only easy things with Powershell and I found it much nicer than classical shells. It's more consistent in the command names and parameter passing. You also need to learn far fewer commands, because Powershell follows the Unix philosophy of small tools that do one thing well much more than Bash+Unix tools. For example if you do "ls" then you get a table where one of the columns is LastWriteTime. Want to sort by t…
Just one more way that ms produces developers that cant do anything on their own, or outside visual studio. Just my experience, but most ms developers have been crippled by their tooling. Powershell is no exception.
"You're weak and have been crippled by your tools."
o_o You're suffering from Stockholm Syndrome. Upgrade your tools and be free from menial labor.
Earlier quoted context omitted.
Windows lacks fork(), or at least it's not documented. To implement the Cygwin folks have to go through a lot of tricks to implement it. And one of them is rebasing all dlls to start at different addresses. There is a tool to rebase everything, and it's usually started after install. It's possible that after you have recompiled your own apps/dlls they might need rebasing too (speaking as a cygwin user, not developer)…
> Windows lacks fork(), or at least it's not documented. The NT kernel supports forking, but the Win32 subsystem does not. Because Interix lives outside the Win32 subsystem, it can provide a proper fork() implementation, whereas Cygwin has to live with its somewhat brittle emulation.
I've switched to powershell ISE on windows (shipped with it) rather than cmd hosted powershell. Does the job!
Earlier quoted context omitted.
> Windows lacks fork(), or at least it's not documented. The NT kernel supports forking, but the Win32 subsystem does not. Because Interix lives outside the Win32 subsystem, it can provide a proper fork() implementation, whereas Cygwin has to live with its somewhat brittle emulation.
Maybe I misunderstand this, but couldn't someone write a driver for Cygwin to have a better fork implementation?
I don't see Microsoft adding forking support to the Win32 subsystem any time soon, so you'd end up rewriting Cygwin from scratch by reverse engineering Interix...
Earlier quoted context omitted.
I'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!
perhaps the real solution to the performance issue you mention is to have svnadmin actually write to a target file instead of crossing process boundaries to redirect stdout ? have you tried : Start-Process '{PATHTOSUBVERSION}\svnadmin' -argumentlist "dump {PATH_TO_REPOSITORY}" -RedirectStandardOutput c:\temp\repodump.dmp -Wait more examples here : http://www.youtube.com/watch?v=9sn2L0E5jT8
Unfortunately its very verbose for a simple case which works fine in cmd so I'm not sure that it warrants using that tool
Looks 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/ I'm not sure if clink and Console will work together, but I'll have to try it.
Console2 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/ Scott Hanselman wrote a blog post about it: http://www.hanselman.com/blog/ConEmuTheWindowsTerminalConsol...