No offense, but I think you are suffering from being used to one thing and missing it when you don't have it. I've worked 20 years as a programmer, about half in a Windows environment and half in an embedded/Unix environment. When programming in an embedded or Unix environment we always used the GNU tool chain because it's what all of the programmers preferred.
Anyway, I vastly prefer the available free software tools over any proprietary platform. For example, for source management, nothing beats Git (well, I can understand why some people prefer Mercurial, but that's free software too). I've used Perforce, Clear Case, and (god help me) Source Safe. They slow me down dramatically. For build management, a lot of Windows programmers use the tools built in to Visual Studio, but this makes continuous integration virtually impossible. I want a continuous build running. I want to know if a check in broke the build immediately, not a day later. All of the best continuous build tools are free software (and many of them have Visual Studio plugins in case you just can't wean yourself from it). Are there any TDD frameworks that aren't free software in existance??? I don't know of any. For build tools, if I'm writing C++ or C the Auto tools are dramatically better than anything I've ever seen on Windows (though I admit they are *very* cryptic and require time to learn). For other languages, I just tend to use whatever the language provides -- Ant for Java, Rake for Ruby, whatever. There are some IDE tools, but they only really work in Mickey Mouse situations, not in large software projects.
There are a couple of places where I'll give the nod to some of the proprietary software tools. Personally, I like vi (and even Emacs -- I'm bilingual) along with exuberant ctags. I'm dramatically more productive with that than with any IDE I've tried (and I probably have tried them all). The one place where Visual Studio excels is in refactoring tools. But in the end, not having them doesn't slow me down enough to use VS. If you are used to VS, I can see why you wouldn't want to learn anything else. Editors are really personal. It's a pity that people choose to learn tools that are only available on a single platform, but there you go...
For writing a manual.... Seriously, Word???? That's just nuts. You can't write a decent manual in Word because you just don't have the typesetting features. I suppose if it's not a professional manual (which is why a programmer is writing it)... I wouldn't use Open Office either. If I had to write a manual, it would certainly be LaTeX, which would give me good output and would be much easier to write to boot. You do have to learn, it though. Having said that, there are no particularly good typesetting packages available in free software that a documentation expert would likely want to use. But Word also fits that description.
As for having to use the command line... You *are* a programmer aren't you? Seriously, scripting is your friend. You save soooo much time. I think you are used to doing things one way and even though the new way is dramatically better, you aren't used to it. There's a reason why people used to working on Unix like systems haven't embraced the point and click programming IDE. Command line interfaces and specially built tools that do their task exceptionally well are much, much, better.
It's a pity, because I've met many programmers like you when I worked in Windows-only shops. It doesn't take that much time to show the benefit of the tools available in a free software environment. But if you don't know, then you don't know.