[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- To: BUG-ZWEI at MIT-AI
- From: Philip E. Agre <AGRE at MIT-AI>
- Date: Sun ,6 Jun 82 12:58:00 EDT
In zwei in Experimental Remote-File 10.0,
Experimental LMFILE-Remote 17.1, Experimental MIT-Specific 9.0,
Experimental System 86.18, Experimental ZMail 45.0, microcode 123, gc@18, on Lisp Machine Six:
There seems to be a new feature in C-P and C-N whereby the "remembered" column
position of the cursor is relative to the screen rather than to the text.
This only shows up in lines of text which lie on more than one screen line.
For example, in this line, if you do C-P C-N at the end of the line you don't end up back at the end of the line of text,
but rather one screen line below it. What is the "real" line anyway in
COM-UP-REAL-LINE and COM-DOWN-REAL-LINE, the text line or the screen line? If
it's the screen line, then C-P at the end of that line should have stayed on
the same screen line. If it's the text line, then C-P C-N should have gone
back to the same text column. What may be going on is that the "real" line is
the text line and the "real" column (or "index" as the code calls it) is the
screen column. This isn't consistent. Perhaps one could have a user-settable
switch that says whether the "real" line and column are the text line and
column or the screen line and column. Maybe some people like it inconsistent,
so perhaps two switches are in order. In any event, I don't like this new
feature. Is there some easy way I can have my init file tell Zwei to do it
the old way? From my reading of the code, the problem is pretty deep-seated
and simply redefining DOWN-REAL-LINE or even perhaps FORWARD-LINE won't do the
job. (Anyway, I really dislike redefining deep internal functions like that.)