Newsgroups: comp.sys.next
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usenet
From: gad@eclipse.its.rpi.edu (Garance A. Drosehn)
Subject: Command-Arrow_Keys
Message-ID: <fk=lzmq@rpi.edu>
Nntp-Posting-Host: eclipse.its.rpi.edu
References: <9106210910.AA14352@nextasy2.eecs.wsu.edu>
Date: 21 Jun 91 16:55:41 GMT
Lines: 24

dwatola@NEXTASY2.EECS.WSU.EDU (David Watola) writes:
> Eric P. Scott writes:
>  |Command-. is "magic"--intercepted very early on.
> 
> actually, if you are very bold and daring (and possibly a little
> stupid :-) ) you can get rid of this interception.   my guess is
> (i have not actually tried this.  i don't plan to--i'm not willing
> to take the risk) that all you need to do is change the /_handleCommand
> routine in /usr/lib/NeXTstep/windowPackage.ps.  this routine is
> the part of the window server code responsible for squirreling away
> command-. and taking care of command-uparrow and command-downarrow.

While the idea of intercepting the command-. key sequence seems like an  
*extremely* silly thing to do, the above did remind me of something else I  
wanted.  It'd be nice (perhaps) if command-right_arrow and command-left_arrow  
cycled you thru the windows of the active application.  Basically I want what  
option-right_arrow and option-left_arrow do in Stuart, but I want that for all  
applications.

Would that be easy to do?  Anybody else think it would be worth doing?
 -  -  -  -  -  -  -  -
Garance Alistair Drosehn   = gad@rpi.edu  or  gad@eclipse.its.rpi.edu
ITS Systems Programmer                       (handles NeXT-type mail)
Rensselaer Polytechnic Institute;  Troy NY  USA
