[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: KMP at MIT-MC, (BUG LISP) at MIT-MC
- Subject: (CURSORPOS 'R/S)
- From: GLS at MIT-MC (Guy L. Steele, Jr.)
- Date: Tue, 24 Jul 79 20:40:00 GMT
- Original-date: 24 JUL 1979 1640-EDT
The original theory behind omitting R and S from the cursorpos command set
was that they are only a one-level stack, and LISP sometimes uses (or used to use)
them, and if LISP did then it woulld screw whatever the user was doing.
You can always get the effect (somewhat less efficiently (?)) by just
readin the cursor position yourself and then restoreing it.