Anon> Hi, I am looking for a text editor for programming, which is
Anon> GUI based (the editor, not the code).
For text editing, why GUI?
Anon> I have tried VIM, and
Anon> Xemacs, and although they might be really good for the
Obviously, you haven't tried (X)Emacs seriously enough. You failed to
discover the following features:
Anon> I'm looking for something along the lines of
Anon> textpad or visual slickedit(for windows). I would like
Anon> color highlighting of code,
Anon> goto line # options,
Anon> and to be able to hook it up to a compiler....
When the error messages appear, hit C-x ` (eqv. M-x next-error) to
jump to the offending lines.
Anon> I usually use C++ or Java.
For Java, don't miss the JDE package for Emacs.
And of course, as a programmer, you should learn to use M-x
global-set-key to bind any key to any function that you use
frequently. E.g. I myself bind F9 to "M-x compile" and F8 to "M-x
next-error" so that I can easily invoke the compiler and jump to the
offending lines. (Such a binding of F8 and F9 is a tradition from
Borland's text-based IDE.)
And all the above mentioned features of (X)Emacs do work even when you
run it under a text-only console.
Anon> I have used eclipse, and it is pretty nice, but it runs
Anon> really slow on my machine, and I don't really like the
Anon> "project" approach where it sometimes seems difficult just
Anon> to open a file and edit it, then try to compile it.
So, go Emacs!
"Project" is a stupid idea when it is something compulsory. I'd
prefer a Makefile approach, which is so much more flexible. With GNU
make, you can even go without a Makefile: just do a "make myprog" and
it will automatically discover your myprog.c and invoke gcc to compile
Anon> If I need debugging I don't mind opening it in there but the
Anon> program is too large and slow when all you want is clean
Anon> text editing.
In Emacs: M-x gdb
Anon> I also would like it to not add in a bunch of formatting
Anon> (like some editors which seem like word processors).
Anon> Although, being able to set tab spacing etc, is pretty nice.
(X)Emacs and vi(m) allow you to set tab spacing. However, my
experience is that it is a very very bad idea to use a non-default
(i.e. 8) tab spacing and RELY on it to do code indenting. The
indentations will get messed up once you open it in an editor/viewer
that has a different tab space setting. You'll end up spending more
time on customizing EVERY tool to get the tab spacing right. Don't
forget the printing tool! Disk space is now cheap. It justisfies to
use the space character to do indentation rather than the TAB
character. That could save you lots of troubles. With compression,
the penalty vanishes. (In (X)Emacs, pressing TAB _key_ while editing
a C/C++/Java file would insert enough spaces (not TAB characters) to
get the indentation right.)
Anon> If anyone has any suggestions please let me know! Thanks
Learn (X)Emacs more seriously.
Home page: http://www.informatik.uni-freiburg.de/~danlee