Newsgroups: comp.editors
Path: utzoo!telly!eci386!jmm
From: jmm@eci386.uucp (John Macdonald)
Subject: Re: vi:Too much macro text
Message-ID: <1991Mar12.184615.3940@eci386.uucp>
Reply-To: jmm@eci386.UUCP (John Macdonald)
Organization: Elegant Communications Inc.
References: <1991Mar7.203635.1190@monu6.cc.monash.edu.au> <1991Mar09.003517.5155@convex.com>
Date: Tue, 12 Mar 91 18:46:15 GMT

In article <1991Mar09.003517.5155@convex.com> tchrist@convex.COM (Tom Christiansen) writes:
|From the keyboard of edp328j@monu6.cc.monash.edu.au (3B Systems Support):
|:
|:pete@TIRS.oz.au (Peter Bartel) writes:
|:
|:> Having incorporated a lot of Tom Christiansen's macros (thanks Tom)
|:> into my .exrc, I now find that when I start vi or source .exrc I get:
|:>     Too much macro text
|:
|:A common cause of this is editing a file in $HOME when $HOME/.exrc
|:exists - vi happily grabs .exrc twice (the one in $HOME and the one
|:in the current working directory).
|
|Crap.  I'd forgotten that one.  I fixed it in ours.  The ****ing Sun 
|code gets this one wrong, too.  I guess on Suns you better use /bin/ed.
|
|--tom

While I've never tripped over that particular problem, I
would suggest that it can probably be worked around by
setting environment variable EXINIT to "source $HOME/.exglobalrc"
so that it is being included explicitly by name instead of
implicitly because it matches the default name.  However,
I'm not sure offhand whether this will interfere with the
automatic inclusion of a .exrc file that *is* in the
current directory, if you ever really want that to occur.
-- 
Cure the common code...                      | John Macdonald
...Ban Basic      - Christine Linge          |   jmm@eci386