Here's what I use for C, the language I usually code in:
GCC (duh): http://gcc.gnu.org/
Not the fastest, but it's the de facto standard. I like it because of the rather verbose amount of error-reporting it has.
SciTE (or vim): http://www.scintilla.org/SciTE.html
I used to use vim, but I became tired with the dual mode. SciTE has a lot of functionality other major IDEs have, but fewer dependencies.
DDD: http://www.gnu.org/software/ddd/
Better than plain gdb due to the data display, IMHO. Somewhat flaky though. :'(
Valgrind: http://valgrind.kde.org/
Helps catch many memory leaks and other oddities that get through. It can also be used for profiling.
Splint: http://www.splint.org/
Nazi meet Lint. Catches common coding mistakes and potential errors that may cause vulnerabilities. It makes gcc -Wall look amazingly terse.
Cscope: http://cscope.sourceforge.net/
Really useful for code exploration. Allows nice things like searching for function callers, cross-referencing, etc.
doxygen: http://www.stack.nl/~dimitri/doxygen/
Meant to be used for documentation of a program, but I mostly abuse it for the dependency graphs and other toys. Really handy for code exploration.
indent: http://www.gnu.org/software/indent/indent.html
Because we all like uniform code.
What do you use (for whatever language)?
> Not the fastest, but it's the de facto standard. I like it because of the rather verbose amount of error-reporting it has.
Verbose... Especially when you get a parse error, and it spits out several screenfuls of error messages that have nothing to do with anything. To be fair, gcc is definitely not alone in this. I dream that one day somebody will make a robust parser for C, but this seems unlikely.
Also, for writing C code, I use gcc, a text editor, and a shell. For writing Perl, I use perl, a text editor, and a shell. For writing Java, I use javac, a text editor, and a shell.
No, I kid, I kid.
I don't write Java.
DOS, TurboC.
Windows, VisualC.
SubEthaEdit: http://www.codingmonkeys.de/subethaedit/
Freebie (for non-commercial use) text editors don't get any better. I have no use for its much-touted collaboration features, but its syntax highlighting and auto-indenting put BBEdit Lite to shame, as far as us freeloading cheapskates are concerned.
When editing over ssh, I prefer vi or its derivatives.
In windows:
http://www.crimsoneditor.com/
I found it mostly because its 1) free, and 2) code colouring can be setup for any filetype, as it have it setup to do colouring of SSA/ASS files as well as all the other common programming languages.
If I'm SSHed in, its pico. I'm too dumb to learn vi, or vim.
notepad foewa!
On Windows I use TextPad, which is excellent but not quite free.
On Unix in textmode, pico, because while it does suck horribly, everything else sucks SO MUCH WORSE. Emacs and vi are both stuck in the seventies as far as user interfaces go, and most other editors seem to be content to be nothing but Emacs or vi clones.
C/C++ - Dev-C++
C# - SharpDevelop
Java - Borland JBuilder X (mainly because I'm forced to by school, though)
i use vim for everything related to editing of text files, so i kind of grew quite attached to it :o
the only choice i got for my compiling needs is gcc.. well, i don't really mind anyway, but i'm often mystifyed by those error messages the compiler spits out from time to time X(.
>>7
tried http://cdsmith.twu.net/professional/opensource/lpe.html yet? i used that one a few times before switching to vim, seemed a-ok to me.
Autoindent? Ahh, one feature I detest. I don't want a text editor to guess what I'll do next (someone tell that to the Microsoft Word group).
Can it be turned off?
RealMan's Compiler Collection: http://somewhere.fscked.org/rmcc/ ;D
Using pico? Like color highlighting? Want a more robust editor with those missing features (like multiple files, inserts, search and replace, dos/unix/mac/unicode text compatibility ?)
I suggest my personal favorite: nano (http://www.nano-editor.org/download.html)
Also gcc is king.
As is DDD. THE COLORS CHILDREN, FLAVEN!
The only thing I'm really missing in pico is a lack of text wrapping, and line numbers. Maybe a very basic auto-indent (just keep the same indentation when pressing return).
>Autoindent? Ahh, one feature I detest.
You've clearly never coded Python.
>Can it be turned off?
Which program were you referring to? If SubEthaEdit: Preferences, Edit, uncheck "Indent new lines."
Syntax hi-lighting is nice and all, but I use pico when I'm SSHed into this server through PUTTY, so any colour hi-lighting is lost.
Unless of course, you know a way of turning it on.
>>13
nano fixes all of those problems.
I always call nano with the switches "-wiR".
You can permanently set them in your ".nanorc" file.
-w meaning don't wrap lines
-i meaning auto-indent
-R meaning regular-expression search/replace
Err... use nano?
Nano supports color highlighting, not pico.
And PuTTY has ANSI, linux, and xterm emulation modes, so use one of those to get the color to show up on your end.
>>18
What version of nano is it?
Anything > 1.2.0 supports it. Just create the file in your home directory.
Add the following lines to the file to get the effect of -wicT4m
set nowrap
set autoindent
set const
set tabsize 4
set multibuffer
Have they come up with a standard place for storing configuration files yet? I'm probably not the only one who finds doing a ls -a results in 90% of listings being hidden files.
I've noticed a few rare programs beginning to stuff their files into .config/ Is this an abberation, or has someone (ie: freedesktop) been attempting to finally fix that mess with some sort of standard?
Well...
I think the thing is it shouldn't matter, because the files are supposed to be hidden. However, I applaud application suites (ooffice, gnome, kde, matlab, moz/ffox) who bundle multiple files into one dot-subdirectory.
It wouldn't be freedesktop, I don't think. It's the FHS guys who should say something.
It shouldn't matter, except when it comes to people who compulsively always type "ls -la". I actually have to concentrate if I want to type just "ls" since it's all motor reflex. >.>;