Andy Ross wrote: > > I could jump in and talk about specific tools, and all the Emacs LISP > code that does what you want, but I'll let other people do that. From > the way your question is phrased, I interpret that you are trying to > make your Linux environment work just like the development environment > you had in Windows.
I don't need the exact development environment. I need a development environment where I can start with a quite high productivity (who of us got spare time?). This doesn't rule out the posibility to become even more productive by using other tools more and more over the time. > With all due respect, don't bother. Go back to windows. :) Well, as all of us know there are more important things to Linux than only development environments... > The truth is that the Unix development toolset is just *different* > than what you're used to. If you're not willing to change the way you > work, and even the way you think about problems, you're not likely to > get any use out of the new platform. I'm willing to change. But don't throw me in the cold water (german proverb). Learning is a time consuming task. > Unix is all about small tools that work really well in combination -- > stuff like using the "find" command to grab all the source files under > a directory and piping the output through grep, sed, sort and uniq to > count all the places where a symbol is used. And a good IDE takes use of those and hides the nasty stuff (unrecogniceable environment parameters) from the user. Have you seen the CVS integration into KDE 3.0 (the version of SuSE 8.0)? That's neat! Or the CVS integration in JBuilder? Why would I need to *learn* (difficult tasks can be looked up) the command line options of it? > An IDE will let you do any one of these tasks more quickly than the > command line tools will. But the simpler, more flexible tools are > applicable to whole ranges of problems that the IDE authors haven't > thought of, and it is *THAT*, more than anything else, that makes Unix > such a magnificently productive environment. That's why I want the best of both worlds: an IDE *and* a powerfull shell. They aren't contradicting. > Once you grok it, you'll never go back. But if you go into the > project expecting everything to be the way it was before, you'll only > be disappointed. No, I'm not expecting everything to be the same. But I expect a way to be productive from day 1. As written earlier: I didn't like EMACS as I tried it (c'mon, which sane person programms in LISP?). I'll rather try vi (I'm also using it on a few big HPUX at work). Oh, AFAIK you can replace the internal editor of KDevelop with VIM if you want... CU, Christian -- The idea is to die young as late as possible. -- Ashley Montague Whoever that is/was; (c) by Douglas Adams would have been better... _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
