From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (qmail 24079 invoked from network); 12 Dec 1998 03:43:01 -0000 Received: from mail.redhat.com (199.183.24.239) by lists.redhat.com with SMTP; 12 Dec 1998 03:43:01 -0000 Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219]) by mail.redhat.com (8.8.7/8.8.7) with SMTP id WAA31158 for ; Fri, 11 Dec 1998 22:35:36 -0500 Message-Id: <199812120335.WAA31158@mail.redhat.com> To: blinux-list@redhat.com Subject: Re: Editing through a Terminal? Date: Fri, 11 Dec 1998 21:35:36 -0600 From: Martin McCormick List-Id: For the last 8 years or so, I have used mskermit on a P.C. as a VT100 terminal and vi on UNIX boxes ranging from DEC Ultrix to IBM's AIX. As long as the system knows what type of terminal one is supposed to be, it works like a charm. Just this year, I found out about all the neat things one can set in vi. My favorite is :set wrapmargin=10 or 20 or whatever. The number is the number of characters from the right hand margin that will trigger a new line of text. the vi's I have used wrap on word breaks which is almost like a word processor. If a word is so long that it looks like it will go past the margin, vi just suddenly reprints it on the next line which means that one can just type and not have to worry about the right margin. As for the screen reader, it is a home-grown one I wrote in 8086 assembler about 10 or 11 years ago. It can intercept interrupt 10 calls and that's how it reads incoming data if they use the BIOS services. It works best with mskermit in VT100 emulator mode. Martin McCormick WB5AGZ Stillwater, OK OSU Center for Computing and Information Services Data Communications Group