*BSD News Article 2607


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!mips!mips!sdd.hp.com!usc!sol.ctr.columbia.edu!destroyer!news.iastate.edu!help.cc.iastate.edu!michaelv
From: michaelv@iastate.edu (Michael L. VanLoon)
Subject: Re: emacs type editor wanted
Message-ID: <michaelv.712272562@help.cc.iastate.edu>
Keywords: emacs no_vi
Sender: news@news.iastate.edu (USENET News System)
Organization: Iowa State University, Ames IA
References: <1992Jul25.223126.26886@NeoSoft.com> <1992Jul26.054027.28848@coe.montana.edu>
Date: Mon, 27 Jul 1992 21:29:22 GMT
Lines: 21

In <1992Jul26.054027.28848@coe.montana.edu> osynw@warp.mhd.montana.edu (Nate Williams) writes:

>In article <1992Jul25.223126.26886@NeoSoft.com> gclarkii@NeoSoft.com (Gary Clark II) writes:
>>I'm trying to find a emacs type editor that has already been ported to
>>the 0.1 version of 386BSD.  I can get GNU Emacs, but I'm trying to avoid
>>the size (I only have about 30 megs free...).  I really do hate vi though.

>I just ported (not really) uemacs 3.11a to 386BSD.  I grabbed the source
>I had for the DECstation, and I had to change two lines in one of the
>files to include <sys/ioctl_compat.h> just before <sys/ioctl.h>, and 
>things compiled w/out a hitch.

This is the second piece of software I've seen that needed this (the
other was an ircII client I was compiling).  Is there any good reason
why <sys/ioctl.h> shouldn't just include <sys/ioctl_compat.h> by default
for every compile?
-- 
------------------------------------------------------------------------------
Michael L. VanLoon                                     "Ignorance is bliss..."
michaelv@iastate.edu      --       Computer Engineering, Iowa State University
------------------------------------------------------------------------------