On Sep 26, 2008, at 10:01 AM, Peng Zang wrote:
So, if gedit has a programmatic interface you can write
shell script to parse the compilation errors (just look for line
numbers) and
send a command to gedit to go to the appropriate line. I don't
know if gedit
has that capability, but certainly there may be other text editors
that do.
such as nedit -- see script below.
On Sep 26, 2008, at 3:09 PM, Nathaniel Gray wrote:
On Fri, Sep 26, 2008 at 5:10 AM, Brighten Godfrey
<[EMAIL PROTECTED]> wrote:
I use, on a daily basis, a small script which acts as a front-end
to `make'
and automatically points you to the error in the code in nedit,
highlighting
the characters that the ocaml compiler complains about. It uses the
existing nedit window if you have the file open already, or else
opens it
for you. The script also works with gcc instead of ocaml, and
(though I
can't vouch for it much) gvim instead of nedit. So my typical
development
environment consists of nedit and a shell in which I compile via
the script.
If anyone is interested, I'd be happy to share this.
I for one am interested -- that could come in handy!
OK, here it is:
http://www.cs.berkeley.edu/~pbg/mindy/
~Brighten
_______________________________________________
Caml-list mailing list. Subscription management:
http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
Archives: http://caml.inria.fr
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
