Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site allegra.UUCP
Path: utzoo!watmath!clyde!akgua!mcnc!decvax!harpo!ulysses!allegra!alan
From: alan@allegra.UUCP (Alan S. Driscoll)
Newsgroups: net.unix-wizards,net.bugs
Subject: Re: MAJOR BUG (mode lines)
Message-ID: <2433@allegra.UUCP>
Date: Sun, 22-Apr-84 16:27:55 EST
Article-I.D.: allegra.2433
Posted: Sun Apr 22 16:27:55 1984
Date-Received: Mon, 23-Apr-84 07:12:00 EST
References: <147@uthub.UUCP>, <377@ucbvax.UUCP>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 20


> (1) vi/ex reading commands from its source files.  I reluctantly have to
> 	agree that this is a bad idea.  I can see where it would be very
> 	useful, but I think the dangers outway the advantages.
> (2) vi/ex reading .exrc from current directory and home directory:
> 	This one IS a good idea.  It can take the place of some of the 
> 	things that (1) was supposed to do.  Different types of files
> 	often require different configurations.  For example, 
> 	'autoindent' is very useful when writing a program, but a pain in
> 	the rear when typing text.  I like the idea of vi being 
> 	automatically reconfigured for these different tasks.

What if you have different sorts of files in the same directory?  Don't
you really want your editor's configuration determined by the extension
of the file you're editing?  That way, you get autoindent on '.c' files,
etc.  Gosling's Emacs has such a facility.

-- 
	Alan S. Driscoll
	AT&T Bell Laboratories