[comp.os.minix] vi : timer alarm

nt@otter.hpl.hp.com (Nicolas Tripon) (06/04/91)

IBM PC-AT compatible, 4 Mo RAM, 20 Mo hard disk, Minix 1.5.
1) During a vi session, I got a "Timer Alarm" message on the screen, and
   the computer got stuck. What does the message mean ?
2) The couple (readall, badblocks) does not work properly on my system : the
   controller continues to stumble on bad blocks after they were supposed to 
   be marked as such. Where could I find a corrected version of these 
   programs ?
Regards. -Nicolas Tripon

dal@hpfcso.FC.HP.COM (Dan Linzmeier) (06/25/91)

>/ hpfcso:comp.os.minix / nt@otter.hpl.hp.com (Nicolas Tripon) /  3:45 am  Jun  4, 1991 /
>IBM PC-AT compatible, 4 Mo RAM, 20 Mo hard disk, Minix 1.5.
>1) During a vi session, I got a "Timer Alarm" message on the screen, and
>   the computer got stuck. What does the message mean ?
>2) The couple (readall, badblocks) does not work properly on my system : the
>   controller continues to stumble on bad blocks after they were supposed to 
>   be marked as such. Where could I find a corrected version of these 
>   programs ?
>Regards. -Nicolas Tripon
>----------

I have not seen a response to question (1) on the net so I thought I would
send one out.  The man page on elvis (under keytime option) talks about
keycodes for arrow keys.  It mentions that some keyboards return a slow
escape sequence for an arrow keycode (or someting like this).  Elvis does
not like the ESC key in command mode. 

I am a sloppy vi'er and hit the ESC key while in elvis's command mode.  This
triggers the Alarm Clock message (after some delay).   Interesting enough,
if the option kt (keytime) is set to any number (not just zero), the
problem goes away (it does not work well when it is left uninitialized).

I set the keytime option to zero in a .exrc file in my home directory.
Alternatively, you can do a  (:set kt=0) in elvis for every session.

Enjoy - Dan Linzmeier

(I am changing jobs and unreachable at present).