Original Post
🔒 Locked
Linux C++ IDE
Advertisement
quote:
Original post by subnet_rx
What does everyone use here? I''d rather have an IDE rather than just using something like Emacs.
Use Vim or Elvis - they''re better. If you really want an IDE, use KDevelop. It''s pretty good.
I use KDevelop, and I think it''s great. I''ve tried Anjuta, but the stupid thing never seemed to pay any attention to my settings, and to force me to use a src/ directory for all my file is just plain annoying. So, KDevelop it is! 
-------------------------------------------------------------
LGPL 3D engine - http://www.sourceforge.net/projects/realityengine
-------------------------------------------------------------
LGPL 3D engine - http://www.sourceforge.net/projects/realityengine
I just started seriously using linux myself. I''ve been testing almost all of the ones suggested.
I definetly think anjuta is the way to go. KDevelop is alright but the big drawback imo is that you have to create project no matter what (at least I couldn''t see a way to do a single file). Anjuta does single files as well as projects and when it does do projects it seems to have less overhead than kdevelop.
fyi My windows programming is mainly done with borland products so that you know where I''m coming from.
I definetly think anjuta is the way to go. KDevelop is alright but the big drawback imo is that you have to create project no matter what (at least I couldn''t see a way to do a single file). Anjuta does single files as well as projects and when it does do projects it seems to have less overhead than kdevelop.
fyi My windows programming is mainly done with borland products so that you know where I''m coming from.
Emacs or vi, what more could you want?
IMHO, vi is just plain horrible. Any editor where you need to enter cryptic commands before you can start editing is a Bad Idea.
Personally, I like jed and pico/nano for console editing. However, I usually find myself writing everything with loads of kwrite windows opened in KDE :}
I did try KDevelop, but I didn''t really like the "feel" of it. I also tried Anjuta in its early days. Maybe I should give it a try once more.
Oh, and I''m using plain Makefiles for everything but the simplest projects because I''m just too lazy to figure out how to set up autotools + dynamic libraries.
cu,
Prefect
Personally, I like jed and pico/nano for console editing. However, I usually find myself writing everything with loads of kwrite windows opened in KDE :}
I did try KDevelop, but I didn''t really like the "feel" of it. I also tried Anjuta in its early days. Maybe I should give it a try once more.
Oh, and I''m using plain Makefiles for everything but the simplest projects because I''m just too lazy to figure out how to set up autotools + dynamic libraries.
cu,
Prefect
quote:
Original post by Prefect
IMHO, vi is just plain horrible. Any editor where you need to enter cryptic commands before you can start editing is a Bad Idea.
But when push comes to shove, vi kicks ass. It''s small, fast and powerful, and those "cryptic commands" eventually save you a ton of keystrokes/mouse movement when you get used to them. vi was my sole "patnah" when performing recovery operations on my system, though I prefer emacs as a source editor. It has its quirks but it''s still the most powerful *nix environment (some say emacs is a desktop).
However, Kwrite is still pretty cool.
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement