I''ve used older versions of both Anjuta and KDevelop, and wasn''t too impressed by either. Anjuta was certainly not bad, but there were a few things about it that annoyed me.

KDevelop, on the other hand, has apparently improved a great deal with the latest release, and I''m willing to give it another try now.

Go for KDevelop 3. You will find troubles understanding how to make/use libraries, but you''ll get used to it with time.

If you really want to learn do a simple "hello world main()" for console with a text editor and then write a simple make file for it. Then add complexity to it, until you can''t handle to write the makefile by yourself, and then go with kdevelop.

Motor is good and easy also, but it runs in console only.

quote: Original post by Armand
Sorry VI is not this. It is an excelent editor, but easy to learn all of its power is not easy.

I strongly disagree

Vim and Xemacs/Emacs scare the beejezus outta me. I start looking at all the keyboard control shortcuts and my head starts swimming. I think CoolEdit is about as deep a hard-core editor as I want.

I''ve only played around with Anjuta, though I have to admit, I only make toy programs, so I''m not sure how scaleable it is when your projects start getting big.

BTW, I saw a book on GCC for 50$ that looked interesting. It gave all sorts of tips and information on how to do lots of things from the command line with GCC. Since I''ve only worked with Anjuta, it was interesting (though obviously complex). But at least it gave me an idea of some of things that were going on while compiling (I always wondered what -Walloff was). However, GCC is a bit more than I can chew off for right now, as even understanding makefile rules, targets and dependencies can be a bit challenging for me right now. Why learnmakefiles if I''m using Anjuta? Because when I look at Anjuta''s pre-built makefiles, I have absolutely no clue what in the hell its doing.

Sometimes I''ve tried to "debug" a tarball compilation that wouldn''t compile by looking at the makefile to see what it''s doing. So I think at least learning makefiles is a good thing. Maybe once I master makefiles I''ll move on to command line GCC (and maybe even dip my toe into the Vim/Emacs thing).

Just some suggestions to mull over.

quote: Original post by CoffeeMug
I strongly disagree

Actually, look at the vim tutorial. That''s how I learned how to use vim, and now I love it.

Of course, vi I hate with a passion, but you''d have to be an idiot to use vi when vim is available. Emacs also sucks. Stay away from it at all costs.

I used emacs in school and have tried vi. I really like emacs once you get over the learning curve. You can do just about anything with it. I never liked vi that much. Currently though, I use Kdevelop 2.15. I find it is easier for me to manage larger projects with Kdevelop than it is with emacs.

quote: Original post by Interim
I guess I need to pass out laughing gas to get a joke through =)

Joke? I was betting with myself how many posts it took for someone to say "vi" or "emacs". It''s getting old. Really old.

quote: Original post by Dauntless
BTW, I saw a book on GCC for 50$ that looked interesting. It gave all sorts of tips and information on how to do lots of things from the command line with GCC. Since I''ve only worked with Anjuta, it was interesting (though obviously complex). But at least it gave me an idea of some of things that were going on while compiling (I always wondered what -Walloff was). However, GCC is a bit more than I can chew off for right now, as even understanding makefile rules, targets and dependencies can be a bit challenging for me right now.

man gcc - It''s free!

quote:
Why learnmakefiles if I''m using Anjuta? Because when I look at Anjuta''s pre-built makefiles, I have absolutely no clue what in the hell its doing.

That''s automake/conf. It''s functional, but not a good thing to learn makefiles with.

Well, I tried most of the IDEs in linux, I will probably try eclipse with the C++ plugin, but usually I just go back to emacs, I can ssh into my computer and do work, I can also ssh into the CS department''s computers and see if my code compiles under solaris. I don''t really like vi, probably more because I learned emacs first, and really have no need as far as resources are concerned to learn any vi-like text editor.

quote: Original post by Arild Fines

quote: Original post by Interim
I guess I need to pass out laughing gas to get a joke through =)

Joke? I was betting with myself how many posts it took for someone to say "vi" or "emacs". It''s getting old. Really old.

LMAO. Welcome to the Unix community. Most of the arguments pre-date most of the posters on here (maybe not me though, getting old). =)

But, I guarantee if you polled most serious Unix programmers, you''d get a mix of "VIM or EMACS" for their IDE of choice. It''s why I posted the link to some of the OSS community leaders and their tools of choice. Whether people use VIM/EMACs because of a lack of a good IDE or because they simply can''t find an IDE that gives them the text power editing of VIM or EMACs, I don''t know.

I use VI or VIm. Having most of my experience managing internet services on Unix for ISPs, its the one editor I''m guaranteed to find on just about every box on the internet regardless of distribution, distributer, or integrater. Though to be honest, my primary job isn''t programming, so I have not done large projects with VI, But it works for me. In fact, once you learn how to interact with the shell through VI/VIM, I find using editors such as joe, nano and such to be patheticly awkard for most sys admin tasks.

Nothing like pulling up the output of a simple shell command, then running a search and replace from command mode and then saving. Used to take me less than 30 seconds to edit huge DNS zone files, and without writing custom scripts.

Interim