🚀 go-pugleaf

Well, I can't really figure the exact cause of this one out (maybe one
of you with source can tell us?), but when I have a large environment
(random examples: more than 36 environment variables, or totalling more
than about 1100 bytes worth [i.e., no "magic numbers" to recognize]),
invoking vi gives "illegal instruction" ...

More information: I ran trace on it, and there's a write() just before
the core dump that goes to the bottom of the screen, inverts, and says
"missing lhs", gets out of inverted and heads home.  This happens just
after stat()ing the .exrc file, so it must be at the point in the code
where the $EXINIT variable is used ...

Any ideas?

/jordan