Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!cuae2!ltuxa!ttrdc!levy
From: levy@ttrdc.UUCP (Daniel R. Levy)
Newsgroups: net.micro.mac,net.unix
Subject: Re: Re: Porting UNIX Applications to the Mac
Message-ID: <1204@ttrdc.UUCP>
Date: Tue, 30-Sep-86 13:56:34 EDT
Article-I.D.: ttrdc.1204
Posted: Tue Sep 30 13:56:34 1986
Date-Received: Fri, 3-Oct-86 00:22:57 EDT
References: <1572@cbdkc1.UUCP> <1091@hoptoad.uucp>
Organization: AT&T, Computer Systems Division, Skokie, IL
Lines: 26
Xref: mnetor net.micro.mac:7341 net.unix:5729

In article <791@mtund.UUCP>, adam@mtund.UUCP (Adam V. Reed) writes:
>Larry Tesler:
>> ....  A useful definition
>> of mode is a state of a user interface that affects the interpretation of
>> subsequent inputs without obvious indication.  It is possible on the Macintosh,
>> using clover keys, to bring up a dialog box and thus enter a mode unknowingly.
>> But it is exceedingly rare compared with systems like vi that overload the
>> typing keys with functional meanings.
>Although I enjoy the relative orthogonality of vi, I think that some
>visible indication of whether one's input will be interpreted as text
>or commands might be very desirable. But would it really be enough to
>make vi "modeless"?
>					Adam Reed (mtund!adam)

:set showmode

('INPUT MODE' will show up on the status line when appropriate [if you have
also :set terse then there is just an 'I'])
-- 
 -------------------------------    Disclaimer:  The views contained herein are
|       dan levy | yvel nad      |  my own and are not at all those of my em-
|         an engihacker @        |  ployer or the administrator of any computer
| at&t computer systems division |  upon which I may hack.
|        skokie, illinois        |
 --------------------------------   Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa,
	   go for it!  			allegra,ulysses,vax135}!ttrdc!levy