C IDE

Vim

Since when were vi/vim/emacs/etc. IDEs?  The ability to edit text and to colorize syntax does not an IDE make.

Visual Studio is surprisingly excellent, for MSVC or not.  Very nice debugging and deployment features.

Code::Blocks is usually what I download as a minimum at my school's computers, so I at least have something to work with.  Not as full featured, but FOSS and all that.

Netbeans/Eclipse are both good and are equal to each other in regard to C, but Visual Studio seems much better to me if you can obtain a copy, or if you're fine running a trial version to try it out.

DevCpp is terrible, outdated, and should not even be considered.  Never used Beta5, no advice there.

>>19
Integrated Development Environment
Think about it.

>>19
Okay.

vim with an autocompletion plugin, and I assume you also have make, gdb and gcc/clang.

>>19
Cool mail and tripcode, /g/ shitstain.

>>5-8,19-20
vim is a disintegrated development environment. To really do anything with it, you need at to least

 - Install cscope
 - Install ctags (for .S files and other things cscope doesn't understand)
 - Build vim with cscope support (every sane Linux distro's full vim package has this by default)
 - Read if_cscop.txt and paste (some of) their recommended settings into your ~/.vimrc
 - Write some scripts to generate tags and cscope.out (put them in the project makefile if you can)

That's my basic setup and I still ! into the shell all the time to run indent and etc.

>>21
I always tell myself that vimscript plugins for completion or gdb connectivity are just a shitty way to re-implement emacs, and that I'll just give up and switch to evil-mode if I decide I need them. I never get around to it, though - I just use screen to open another window and run gdb or whatever in that. Thus, I'm C-a'ing all over and my emacs envy persists.

>>23
Then use emacs and slowly rupture your carpal tunnel. I couldn't care less about your choices.

>>23
This is why you should use real vi instead. It includes ctags and doesn't need all that other shit.

>>24
rupture your carpal tunnel
That's what evil-mode would be for.

>>25
use a real vi
u mena nvi?

u mena nvi?
No.
http://ex-vi.sf.net/

>>27
I had no idea tags support was present in the original Berkeley vi. Neat!

>>28
The original Ctags was introduced in BSD Unix and was written by Ken Arnold, with Fortran support by Jim Kleckner and Pascal support by Bill Joy.

>>19
im too baka i never could manage eclipse to compile me even a simple 'hello world' -_-
it has way too many buttons and other strange things, so i use geany+gdb/clang

oh, and valgrind of course
does eclipse have an analogue of valgrind?

>>31
Most Java programmers don't care that memory even exists, but surprisingly there is:

http://www.eclipse.org/linuxtools/projectPages/valgrind/

Like every Eclipse plugin, though, it will always lag behind the command line utility.  Tried doing a complex rebase in EGit lately?

install
gvim (or vim-gtk)
vim-clang-complete
vim-supertab

and then, add to your .vimrc
syntax on
set ai si
let g:SuperTabDefaultCompletionType = "context"
let g:SuperTabLongestHighlight = 1
" supertab does clang completion backwards
let g:SuperTabMappingForward = '<s-tab>'
let g:SuperTabMappingBackward = '<tab>'

and just use evim -g

alternatively, you can make a script
# cat > /usr/bin/vim-notepad
#!/bin/bash
evim -g "%@"
^D
# chmod +x /usr/bin/vim-notepad

you'll have ctrl-x/c/v/s cut/copy/paste and save, with nice syntax highlighting and one of the best completions for c and c++

>>32
eclipse has a version for 'c/c++ developers', i mentioned it.. they should make a course how to use it or so because i cannot realize how

emacs

ED!!!

ed man!! !!man ed

>>36
emacs.