Date: Tue, 3 Jan 1995 10:27:22 -0800 (PST) From: Gordon Hogenson To: Michael Feldman Cc: DJGPP List Subject: Re: elvis with djgpp (and other vi clones) On Mon, 2 Jan 1995, Michael Feldman wrote: > > > > On Sun, 1 Jan 1995, Michael Feldman wrote: > > > > > It's not clear to me why elvis should be recompiled. I haven;t installed > > > the binaries yet - are they broken? > > > > > > If elvis is compiled with a commercial compiler (eg BCC) for conventional > > > memory, this is an _advantage_, because it doesn't eat 130k of RAM for its > > > own go32. Why recompile it with djgpp? > > > > I wanted to fix it up so that it would look at the GO32 environment > > variable to set up its video mode. I never got around to hacking that > > in, but that was the original motivation. > > > > Gordon. > > > Ah, now it's clear. But given the go32 memory problem, would this be > worth it? 'Course that problem wil be greatly diminished with version 2. > > Mike Feldman > I guess it turned out not to be worth it, since I never got around to it. I confess, I actually use 'vim' and not elvis, and I use a precompiled binary. Of course now that DJ has built GNU make with version 2 (omnigate.clarkson.edu/pub/msdos/djgpp for those who didn't notice), using a DJGPP-compiled editor becomes more practical, with "only" three copies of go32 in memory at once (is that right? one for the editor, 0 for make, 1 for gcc.exe and one for cc1, et al). I guess if you use gcc-rm.exe that gets you down to two. There might be a problem with Paul Fox's "vile" with DPMI though, if you build it with DJGPP. The docs say it won't run under Windows when built with DJGPP. Since v2 of make requires DPMI, we probably need a DPMI-friendly port of vile to take advantage of the new make. BTW, "vile" is available at id.wing.net:/pub/pgf/vile. Gordon.