From owner-freebsd-ports Mon Dec 2 22: 5: 2 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B53237B401 for ; Mon, 2 Dec 2002 22:05:00 -0800 (PST) Received: from chilled.skew.org (skew.org [216.241.45.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68E9F43E9C for ; Mon, 2 Dec 2002 22:04:59 -0800 (PST) (envelope-from mike@skew.org) Received: from chilled.skew.org (localhost.skew.org [127.0.0.1]) by chilled.skew.org (8.12.6/8.12.6) with ESMTP id gB364uAC062773; Mon, 2 Dec 2002 23:04:57 -0700 (MST) (envelope-from mike@chilled.skew.org) Received: (from mike@localhost) by chilled.skew.org (8.12.6/8.12.6/Submit) id gB364tHD062772; Mon, 2 Dec 2002 23:04:55 -0700 (MST) From: Mike Brown Message-Id: <200212030604.gB364tHD062772@chilled.skew.org> Subject: Re: lrzsz never works for me on FreeBSD (aha!) In-Reply-To: <000501c298b9$2d966d40$0200000a@buttercup> To: ports@freebsd.org Date: Mon, 2 Dec 2002 23:04:55 -0700 (MST) Cc: uwe@ohse.de X-Mailer: ELM [version 2.4ME+ PL90 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dirk Meyer was kind enough to suggest that I use the "-e" option to avoid problems on connections that are not 8-bit clean. This did the trick, but led me to wonder "why is my terminal not 8-bit clean?". I started experimenting some more just now. It turns out that since the dawn of time (10 years at least) I've had this in my .login: if ( ! $?TERMCAP ) then tset -Q '-mdialup:?vt100' $TERM endif There's no TERMCAP environment variable these days, so the tset is invoked. I don't think the 'dialup' business applies nowadays, either, and using the $TERM argument is the default, so the effect is the same as if I had invoked 'tset' or 'reset' with no arguments. For the terminal types I use (vt100 or linux), this is equivalent to making the following changes (assume each flag would normally be the opposite of what it's being set to): stty -echok ixany ignpar oxtabs onocr onlret erase ^? I'm not sure what they all mean, since I'm not well versed in terminal arcana, but surely they are pretty much all problematic: -echok = do not echo NL after KILL character ixany = allow any character to restart output ignpar = ignore characters with parity errors oxtabs = expand tabs to spaces on output onocr = do not output CRs at column zero onlret = NL performs the CR function on the terminal erase ^? = sets the ERASE character to something unhelpful I have no need to invoke tset at all, as far as I know, so I've commented that line out. Man, all these years, never able to use lrzsz for this silly reason. Oh well. One for the archives. Mike -- Mike J. Brown | http://skew.org/~mike/resume/ Denver, CO, USA | http://skew.org/xml/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message