Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ncoast.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!cwruecmp!atvax!ncoast!bsa
From: bsa@ncoast.UUCP (Brandon Allbery)
Newsgroups: net.unix,net.text
Subject: Re: can vi/ex source beginning of text on startup?
Message-ID: <498@ncoast.UUCP>
Date: Tue, 11-Dec-84 16:36:40 EST
Article-I.D.: ncoast.498
Posted: Tue Dec 11 16:36:40 1984
Date-Received: Fri, 14-Dec-84 05:35:32 EST
References: <31@politik.UUCP> <107@bigtuna.UUCP> <1704@umcp-cs.UUCP>
Reply-To: bsa@ncoast.UUCP (Brandon Allbery)
Organization: Unix-like Operating Systems Consultant
Lines: 20
Xref: watmath net.unix:3100 net.text:307
Summary: 

I'm having a problem with .exrc and EXINIT on a Plexus P/35.  I generally
use a standard set of :set's to make C programming easier, and on ncoast!'s
vi, they work well.  But on the plexus, which has the same version (v2.13)
of vi, any attempt to place a :set in .exrc or $EXINIT will produce 
a _N_o_ _t_e_x_t_ _i_n_ _b_u_f_f_e_r
message.  Does anyone know why this might be?  Does the Microsoft-hacked
ex/vi have a smarter $EXINIT handler?  Or am I doing something wrong?

-------------
./.exrc
-------------
set autoindent shiftwidth=4 showmatch autowrite

--bsa
(Just had a thought:  MS ex/vi takes that.  Maybe (from net examples)
the plexus needs a colon in front?  But I put one there in $RNINIT...)
-- 
  Brandon Allbery @ decvax!cwruecmp!ncoast!bsa (..ncoast!tdi1!bsa business)
6504 Chestnut Road, Independence, Ohio 44131   (216) 524-1416
<<<<<< An equal opportunity employer: I both create and destroy bugs :-) >>>>>>