Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!caen!zaphod.mps.ohio-state.edu!rpi!batcomputer!munnari.oz.au!ariel!ucsvc.ucs.unimelb.edu.au!lu!ecsgrt
From: ECSGRT@lure.latrobe.edu.au (GEOFFREY TOBIN, ELECTRONIC ENGINEERING)
Newsgroups: comp.editors
Subject: Re: map the space bar
Message-ID: <5108@lure.latrobe.edu.au>
Date: 27 Feb 91 06:57:01 GMT
References: <984@uncw.UUCP> <2878@gould.doc.ic.ac.uk>
Organization: VAX Cluster, Computer Centre, La Trobe University
Lines: 17

Alexios Zavras (usually zvr@theseas.ntua.gr,
but until Feb.15 at az@doc.ic.ac.uk) writes:

> Although it *is* possible, I would strongly advise against it.
> The space key is actually used internally in vi !
> If my memory is right, the ~ command, (toggle Upper/lower case)
> uses the space to advance to the next character.  So, unless
> you also want to move down half a page when toggling cases
> (and maybe some other times), do not map the space key.

Hold everything!  Is Alexios accurate in stating that mapping
a key will change its INTERNAL usage?  As if in defining "+"
(the plus sign) for the C preprocessor (or in Scheme, or in C++)
will prevent the compiler from doing addition INTERNALLY?
(I exaggerate, but I think not by much.)

GT


Brought to you by Super Global Mega Corp .com