Ah, but I don't use Notepad. I use either gedit with the class browser extension or Scribes. My terminal is Bash, which has fantastic tab autocompletion (with make, for example, it will autocomplete arguments and targets by parsing the makefile) and command history. As a result, I do indeed have code completion. Granted, it is not on quite the same level as an IDE, but handy enough. Scribes keeps a history of words I have written and autcompletes when I write them again. Autosaves, too. It's a really good text editor :)
For documentation, Debian (and Ubuntu) packages a nice application called DevHelp, which organizes every bit of code documentation into one place. I believe Anjuta integrates DevHelp into its own interface, but last I tried the darn thing crashed before I got there.
When I feel like waiting and gazing into a more complex workspace, MonoDevelop is swiftly catching up to fill the rest. I definitely see why people prefer IDEs. Since they are aware of an entire code project, lots of neat stuff can happen like easy refactoring and documentation. Oddly, however, most IDEs do not do this and exist as just glorified text editors. MonoDevelop 2.0 is getting some great features to that end as well as better C bindings, and VS is certainly in a league of its own.
Still, I have a disturbing preference for the more "cody" workspace.
What I like in that territory is I don't really ever think about what my development environment supports; the GTK Source View widget, used by most of these text editors, has never not had a highlighter I need, so I can just get straight to typing in my chosen gibberish with no lost or changed features. Granted, that's mainly because the features weren't there to start with, but the key is that it makes the transition from place to place easier. Every tool thus feels the same, which I think is useful and helps keep the surroundings consistent.
For documentation, Debian (and Ubuntu) packages a nice application called DevHelp, which organizes every bit of code documentation into one place. I believe Anjuta integrates DevHelp into its own interface, but last I tried the darn thing crashed before I got there.
When I feel like waiting and gazing into a more complex workspace, MonoDevelop is swiftly catching up to fill the rest. I definitely see why people prefer IDEs. Since they are aware of an entire code project, lots of neat stuff can happen like easy refactoring and documentation. Oddly, however, most IDEs do not do this and exist as just glorified text editors. MonoDevelop 2.0 is getting some great features to that end as well as better C bindings, and VS is certainly in a league of its own.
Still, I have a disturbing preference for the more "cody" workspace.
What I like in that territory is I don't really ever think about what my development environment supports; the GTK Source View widget, used by most of these text editors, has never not had a highlighter I need, so I can just get straight to typing in my chosen gibberish with no lost or changed features. Granted, that's mainly because the features weren't there to start with, but the key is that it makes the transition from place to place easier. Every tool thus feels the same, which I think is useful and helps keep the surroundings consistent.