home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!ames!sun-barr!west.West.Sun.COM!news2me.EBay.Sun.COM!cronkite.Central.Sun.COM!texsun!exucom.exu.ericsson.se!s09a05!exuhag
- From: exuhag@exu.ericsson.se (James Hague)
- Newsgroups: comp.os.msdos.programmer
- Subject: Re: Suggestions wanted: A good programmers
- Message-ID: <1993Jan21.145517.23060@exu.ericsson.se>
- Date: 21 Jan 93 14:55:17 GMT
- References: <1993Jan11.165957.29093@exu.ericsson.se>
- Sender: news@exu.ericsson.se
- Reply-To: exuhag@exu.ericsson.se
- Organization: Ericsson Network Systems, Richardson, TX
- Lines: 24
- Nntp-Posting-Host: s09a05.exu.ericsson.se
- X-Disclaimer: This article was posted by a user at Ericsson.
- Any opinions expressed are strictly those of the
- user and not necessarily those of Ericsson.
-
- James Hague writes:
- >
- >QEdit's big weakness is that it doesn't integrate well with
- >compilers or make utilities. You can call any compiler, yes,
- >and redirect output to a file and load that file into a window.
- >But there isn't a way to nicely jump from one error to the next
- >as most "professional" editors will do. The macro language isn't
- >complete enough to handle the general case of this.
-
- After having talked with SemWare technical support, I found that
- this most definitely _is_ possible. I had misunderstood some of
- the finer points of NextFile and PrevFile. Actually, I was confusing
- the QEdit implementation with a different method used in another
- editor. I have now written macros to jump from error to error using
- makefile output (handles multiple source files, etc.).
-
- >I'm curious if anyone has figured out a nice way around this. I'd
- >switch to QEdit in a second if so.
-
- And so I will. My registration is in the mail.
-
- --
- James Hague
- exuhag@exu.ericsson.se
-