From owner-freebsd-current@FreeBSD.ORG Fri Oct 21 07:00:36 2011 Return-Path: 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 790231065673 for ; Fri, 21 Oct 2011 07:00:36 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 377D28FC0A for ; Fri, 21 Oct 2011 07:00:35 +0000 (UTC) Received: by gyd8 with SMTP id 8so4575343gyd.13 for ; Fri, 21 Oct 2011 00:00:35 -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=CWjvZpBauQq/wkFDbPHe2jwwGm/+3gJNl2EKNOuVPtc=; b=F126Xc6d6G8dymziz5GOa4iUwgG8bKOALx/3qlMWgM0v9AYhnFVmzzU2YL8F4BhQGc MU8/qkm/vDf4IqUsYs/8Paf0Nv0u6ysEN6tNiY53Ljkoc2FZMus7mr7Ix0RJMILJJ0/2 IX5sOnkyT+sitsscYNe35flwP9hAM80zICigY= MIME-Version: 1.0 Received: by 10.182.217.33 with SMTP id ov1mr845788obc.26.1319180435346; Fri, 21 Oct 2011 00:00:35 -0700 (PDT) Received: by 10.182.122.33 with HTTP; Fri, 21 Oct 2011 00:00:35 -0700 (PDT) In-Reply-To: <20111021065912.GE1874@hoeg.nl> References: <20111021065912.GE1874@hoeg.nl> Date: Fri, 21 Oct 2011 00:00:35 -0700 Message-ID: From: Garrett Cooper To: Ed Schouten Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2011 07:00:36 -0000 On Thu, Oct 20, 2011 at 11:59 PM, Ed Schouten wrote: > Hi Garrett, > > * Garrett Cooper , 20111021 08:40: >> =A0 =A0 If I fire up an xterm without setting TERM=3D{ansi,vt100,xterm}, >> [...] > > 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 Thanks, -Garrett