home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!europa.asd.contel.com!howland.reston.ans.net!spool.mu.edu!uwm.edu!ogicse!news.u.washington.edu!serval!luke.eecs.wsu.edu!pmonday
- From: pmonday@luke.eecs.wsu.edu (Paul Monday - CS)
- Newsgroups: comp.os.linux
- Subject: Re: Working term program for Linux?
- Message-ID: <1993Jan26.031230.19468@serval.net.wsu.edu>
- Date: 26 Jan 93 03:12:30 GMT
- Article-I.D.: serval.1993Jan26.031230.19468
- References: <C1Fu8B.I85@ais.org>
- Sender: news@serval.net.wsu.edu (USENET News System)
- Organization: Washington State University!
- Lines: 16
-
- In article <C1Fu8B.I85@ais.org> sno@ais.org (Stephen Opal) writes:
- >Anyway, I've made several attempts at getting minicom to work, with some
- >serious problems. 1) Anything that goes past the 79th column fails to
- >wrap the screen, and I lose the c\r, so several lines of "too long" text
- >will overwrite itself. 2) The BS key sends ^? regardless of the setting
- >(I presume that it is a destructive BS, but somehow doesn't get interpreted
- >that way).
- >So, I'm pretty much ending up having to switch to MSDOS to do much terminal
- >communications. Any clues or alternatives would be appreciated.
- >
- >Stephen N. Opal sno@umcc.ais.org
-
- Yes, someone please divulge the wisdom of being able to clear the screen on
- minicom, I would love to give this @#(& windoze terminal a permanent rest.
-
- thank you
-