From owner-freebsd-current@FreeBSD.ORG  Fri Oct 21 07:15:45 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B8533106566C
	for <freebsd-current@freebsd.org>; Fri, 21 Oct 2011 07:15:45 +0000 (UTC)
	(envelope-from yanegomi@gmail.com)
Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com
	[209.85.161.182])
	by mx1.freebsd.org (Postfix) with ESMTP id 7834C8FC12
	for <freebsd-current@freebsd.org>; Fri, 21 Oct 2011 07:15:45 +0000 (UTC)
Received: by ggnq2 with SMTP id q2so2944535ggn.13
	for <freebsd-current@freebsd.org>; Fri, 21 Oct 2011 00:15:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	bh=T2Jvo/Se50D2q+dYDbkTduDBkDD7AvZMC50hSkSe4BI=;
	b=vxEp6Jfi+8RXgJoxnYWBcDRpd35jxoFgcIZMqYJ9a1ZA9gVoedSClLsRAn694347Ec
	wt7nFaAznmRDkaes52kJpphr8lkMyoHrnlqq3kJH4t1HyrMUjl41WB7Cq1pIdbBSpew3
	hXVi5qGB0im3V2fpaLFSZzfaGSYxXkbRuEsh4=
MIME-Version: 1.0
Received: by 10.182.73.67 with SMTP id j3mr848401obv.46.1319181344857; Fri, 21
	Oct 2011 00:15:44 -0700 (PDT)
Received: by 10.182.122.33 with HTTP; Fri, 21 Oct 2011 00:15:44 -0700 (PDT)
In-Reply-To: <20111021070839.GF1874@hoeg.nl>
References: <CAGH67wSd2Ar1BmZSM5BOWA2r7OvYKX-eCiFtFo2gm1KAH3eOFA@mail.gmail.com>
	<20111021065912.GE1874@hoeg.nl>
	<CAGH67wSjoo_tP3+SXLfiE_oHHTC0LXR7yaJkFuTSEonEqXWXAg@mail.gmail.com>
	<20111021070839.GF1874@hoeg.nl>
Date: Fri, 21 Oct 2011 00:15:44 -0700
Message-ID: <CAGH67wTZ8hVUnt6zfyxxwB-FdBH_GiH0beN6-6oywAAnmfon2w@mail.gmail.com>
From: Garrett Cooper <yanegomi@gmail.com>
To: Ed Schouten <ed@80386.nl>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Not setting TERM explicitly wraps commands at 80 columns with
 nested shells in xterms using sh + bash?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Oct 2011 07:15:45 -0000

On Fri, Oct 21, 2011 at 12:08 AM, Ed Schouten <ed@80386.nl> wrote:
> * Garrett Cooper <yanegomi@gmail.com>, 20111021 09:00:
>> On Thu, Oct 20, 2011 at 11:59 PM, Ed Schouten <ed@80386.nl> wrote:
>> > Hi Garrett,
>> >
>> > * Garrett Cooper <yanegomi@gmail.com>, 20111021 08:40:
>> >> =A0 =A0 If I fire up an xterm without setting TERM=3D{ansi,vt100,xter=
m},
>> >> [...]
>> >
>> > So what's the idea behind this? Why not just set TERM properly?
>>
>> It is set properly though -- that's the confusing part:
>>
>> $ echo $TERM
>> xterm
>
> Oh, okay. So you mean "If I fire up an xterm without changing the
> default TERM, [...]", right?
>
> Can you check whether `stty size' does return the correct numbers? That
> way we can determine if it's a problem in xterm, your shell (or maybe
> the kernel). Thanks!

I'll run that in the next window I find that's acting funky.
Unfortunately my system is behaving properly right now.
Thanks for the tip :)!
-Garrett