[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: MOON at MIT-AI
- From: Mike McMahon <MMcM at MIT-AI>
- Date: Wed ,6 Aug 80 16:14:00 EDT
- Cc: BUG-ZWEI at MIT-AI
- Sender: MMcM at CADR9 at MIT-AI
Date: 6 AUG 1980 0132-EDT
From: Moon at MIT-AI (David A. Moon)
Going into 2-window mode, doing a m-x Occur in one window, then switching to the
other window while leaving the m-x Occur typeout up on the first window does
nasty things. For one thing if the Occur typeout hits a **more**,
selecting the other window with the mouse redisplays the window with the occur
instead of leaving the typeout there. Switching windows with c-x O on the other
hand mostly leaves the typeout there but clobbers the top line.
The problem here is that anything typed or moused causes the more break to be exited,
which causes an end-page exception.
However the real bug is what happens if you click the mouse on the Occur
typeout while the other window is selected; it jumps to that line in the
wrong window but doesn't update the display to indicate what it did.
This then leaves the other window with point outside of its buffer.
(m-< fixes it however).
This bug has indeed been fixed.