Received: (at submit) by bugs.debian.org; 24 Oct 2001 18:21:00 +0000 From dave@lafn.org Wed Oct 24 13:21:00 2001 Return-path: Received: from zoon.lafn.org [206.117.18.9] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 15wSeC-0008Tc-00; Wed, 24 Oct 2001 13:21:00 -0500 Received: from davespc (cs-la1-p38.lafn.org [192.168.9.38] (may be forged)) by zoon.lafn.org (8.11.3/8.11.3) with ESMTP id f9OIKm972255 for ; Wed, 24 Oct 2001 11:20:49 -0700 (PDT) (envelope-from dave@lafn.org) Received: from dave by davespc with local (Exim 3.32 #1 (Debian)) id 15wSfh-0000A4-00 for ; Wed, 24 Oct 2001 11:22:33 -0700 Date: Wed, 24 Oct 2001 11:22:31 -0700 From: David Lawyer To: submit@bugs.debian.org Subject: links browser doesn't work with dumb terminals Message-ID: <20011024112230.A608@lafn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.22i Delivered-To: submit@bugs.debian.org Package: links Version: 0.95 When I try to use links at a Wyse 60 terminal, I see all the escape sequences on the screen. They must be escapes sequences for either vt100 or linux terminals. My WYSE 60 terminal works fine with lynx. Then on my other terminal (almost a vt100) lynx will work only if I set the terminal to no parity and 8-bits/char. But I have it set by default to odd-parity and 7-bits/char and this works fine with lynx, etc. Stty shows the same. Then when I start links, it changes the "stty" settings to no-parity and 8-bits/char. Since the terminal itself (done by the "set-up" key on the terminals) is still set to parity and 7-bits/char, I get mostly error characters on the screen. Links claims to use ncurses which should make it work OK on dumb terminals. But it doesn't. David Lawyer