[11927] in Athena Bugs
eos
daemon@ATHENA.MIT.EDU (wdc@MIT.EDU)
Tue Apr 5 15:27:15 1994
From: wdc@MIT.EDU
Date: Tue, 5 Apr 94 15:27:06 -0400
To: scottcar@MIT.EDU, bugs@MIT.EDU
Cc:
Mercy sakes! I didn't realize this bug had come in PLEASE EXCUSE
my inexcusable tardiness in looking at this.
The reason why you saw the message:
afs: file not saved (above quota or partition full)
was most likely because something went wrong internally inside EZ and it
was core dumping. (Normally we disable core dumps by default, but a
bug in the Sun Operating System prevents us from doing so on the sun.)
So EZ freaked out, got very big, died, tried to save an image of itself, and
ran over your quota in your home directory.
I think I may know what caused EZ to freak out, but it is only a guess.
I fixed a bug in the ^K stuff a while ago, but it may have not made
it out into the world when you were running. If this problem occurs again,
would you resubmit the bug?
As to the bizarre behavior of ^K:
There is a subtle difference between EZ and emacs that has to do with the way
lines appear on the screen. In emacs, if a line does not end with a newline
character (return or enter depending on the keyboard you use),
you get text all the way to the end of the line, a special character
(backslash) telling you something is up, and the rest of the line wrapped
onto the next lines down. If you type ^K at the beginning of this wrapped
line, the whole set of lines up to the return will be killed.
So ^K kills to the next newline, and you see a backslash at the end of
the line if you don't have a newline.
In EZ, because we are dynamically formatting paragraphs to look nicely,
if you don't have newlines, you will not see any indication that they are
abscent. When you type ^K, you will often see a whole paragraph get killed.
When this happens, just type ^Y to yank it back. Hightlight the text you
specifically want to kill, and use ^W to wipe it out.
There is one case in EZ when if you type ^K nothing will appear to happen.
THis is if you have spaces or tabs along a line. ^K gets rid of them.
The effect is, if you have a blank line, sometimes one ^K gets rid of it,
and sometimes two do.
Now, if you hold down the ^K key for a long time, MANY MANY ^K's are sent.
EZ will dutifully record that you've typed the key, and try to handle it as
soon as it has time. (Like a little after you finally let go of the key.)
If you have lots of other stuff going on, or if something I don't know about
is broken inside EZ, it may freak out over all these ^K's that it has
to process.
-wdc
after you stop typing.
