From owner-freebsd-questions Wed May 29 6:10:39 2002 Delivered-To: freebsd-questions@freebsd.org Received: from empty1.ekahuna.com (empty1.ekahuna.com [198.144.200.196]) by hub.freebsd.org (Postfix) with ESMTP id EADA437B400 for ; Wed, 29 May 2002 06:10:34 -0700 (PDT) Received: from pc-02 (pc02.ekahuna.com [198.144.200.197]) by empty1.ekahuna.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com; Wed, 29 May 2002 06:10:34 -0700 From: "Philip J. Koenig" Organization: The Electric Kahuna Organization To: questions@FreeBSD.ORG Date: Wed, 29 May 2002 06:10:36 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: grep and console width Reply-To: pjklist@ekahuna.com Cc: Roman Neuhauser In-reply-to: <20020529120526.GD18367@freepuppy.bellavista.cz> References: <20020529114249806.AAA471@empty1.ekahuna.com@pc02.ekahuna.com> X-mailer: Pegasus Mail for Win32 (v3.12c) Message-ID: <20020529131034381.AAA484@empty1.ekahuna.com@pc02.ekahuna.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 29 May 2002, at 14:05, Roman Neuhauser boldly uttered: > > From: "Philip J. Koenig" > > Date: Wed, 29 May 2002 04:42:51 -0700 > > > > On 29 May 2002, at 12:13, Roman Neuhauser boldly uttered: > > > > > > From: "Philip J. Koenig" > > > > Date: Wed, 29 May 2002 02:41:46 -0700 > > > > Subject: Re: grep and console width > > > > > > > > On 29 May 2002, at 10:34, Roman Neuhauser boldly uttered: > > > it's $COLUMNS, sorry. > > > > > > > set | grep -ai colu > > > COLUMNS=80 > > > > > > but I think I misunderstood what you said. you meant you set your > > > console to the 132x43, which is just fine. :) > > > > > > No COLUMNS variable either. FWIW I'm using tcsh on the machine in > > question. Maybe I need to add something to my .cshrc or .login... > > > > (I tried "setenv COLUMNS 80", but it didn't help the situation in > > mutt - when I press F1, the text still looks like a mess unless I > > change to 132 cols) > > hm. I use zsh, and the variable *is* there; apparently, it's > readonly. > > btw, I just pressed in one of mutt's screens, and now I know > what you're talking about. the problem is in the file itself, > /usr/local/share/doc/mutt/manual.txt. delete the first 7 columns in > the file (it's just indent), and the text will be legible again. > > 6lGx:wq! should take care of it. :) > > the lines are simply too long to fit in a standard console, and > breaks on the 80'th char, and the on LF. Pretty bizarre. Is that a fairly recent version? (I still have 1.2.4 on the box in question) The reason I assumed it wasn't mutt-specific is that I've occasionally run into similiar situations where stuff that seemed absolutely unlikely to not be designed for 80-col displays, wrapped in a similar way. (ie as if there was a "left margin indent".) I just wondered if there was some kind of pager or termcap that internally ignored that indent or something. FWIW, on the linux box in a terminal session, mutt 1.2.5-10 doesn't suffer from this problem. -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message