Thanks. I use a fair number of these tools too. I was looking to get into the 21th century with some type of integrated/GUI build/development environment. The biggest thing was to have a tool that con compile errors I click on a link and takes me to the error and on that allows me to put break points graphically and allow a step through (gdb of course doe this in a text mode). The GNUPro and Kdevelop look like nice tools. Thanks, Frank Eljay Love-Jensen wrote: > Hi Frank, > > I use primarily: > + vim (http://www.vim.org/) > + Bash (http://www.gnu.org/directory/GNU/bash.html) > + gdb (http://www.gnu.org/directory/GNU/gdb.html) > + grep (http://www.gnu.org/directory/GNU/grep.html) > + fileutils (http://www.gnu.org/directory/GNU/fileutils.html) > + findutils (http://www.gnu.org/directory/GNU/findutils.html) > + Diffutils (http://www.gnu.org/directory/GNU/diffutils.html) > + Bison (http://www.gnu.org/directory/GNU/bison.html) > + enscript (http://www.gnu.org/directory/GNU/enscript.html) * > + Binutils (http://www.gnu.org/directory/GNU/binutils.html) > + gzip (http://www.gnu.org/directory/GNU/gzip.html) > + Less (http://www.gnu.org/directory/GNU/less.html) > + Sed (http://www.gnu.org/directory/GNU/sed.html) *** > + shellutils (http://www.gnu.org/directory/GNU/shellutils.html) > + textutils (http://www.gnu.org/directory/GNU/textutils.html) > + Perforce (http://www.perforce.com/) ** > + make (http://www.gnu.org/directory/GNU/make.html) > + GCC 2.95 (http://gcc.gnu.org/) > + GCC 3.2 (http://gcc.gnu.org/) > > I do my work through Telnet or SSH. > > HTH, > --Eljay > > * Yes, I use GNU's enscript. > ** I prefer CVS, but this wasn't my decision. > *** I never learned Perl or Awk. Sed does most everything I need.
