Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!cancer.vividnet.com!hunter.premier.net!news.mathworks.com!enews.sgi.com!EU.net!usenet2.news.uk.psi.net!uknet!usenet1.news.uk.psi.net!uknet!dispatch.news.demon.net!demon!slugvine.demon.co.uk!jas From: jas@slugvine.demon.co.uk (John Stark) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Starting up editor from gmake/gcc output Date: Mon, 30 Sep 1996 19:54:06 GMT Organization: Home Lines: 15 Message-ID: <DyK9y6.80@slugvine.demon.co.uk> X-NNTP-Posting-Host: slugvine.demon.co.uk I've installed the NEdit editor from the 2.1.5 CD. It has a client program called NC that passes it a filename and line number given as command-line arguments, to open the file (if not open already) and move to that line. I'd quite like to invoke NC with the first filename/line number if a gcc compilation error occurs. Is there any utility around that tracks the gmake "entering/leaving directory" messages (I need that feature because the source is built in subdirectories), and parses the gcc error messages to allow something like NC to be run? I could write one myself (it would take me less time to write in C than work out how to using awk+sed), but wondered if I could save myself the effort. -- John Stark (at home), Cambridge, UK | mailto:jas@slugvine.demon.co.uk Tel. Cambridge (01223) 573555 | http://www.slugvine.demon.co.uk