From owner-freebsd-perl@FreeBSD.ORG Wed Apr 15 17:03:39 2015 Return-Path: Delivered-To: freebsd-perl@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0BB0D627; Wed, 15 Apr 2015 17:03:39 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D51A4DCB; Wed, 15 Apr 2015 17:03:38 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t3FH4bWA009961; Wed, 15 Apr 2015 10:04:43 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: freebsd-perl@freebsd.org, Matthew Seaman In-Reply-To: <552E936A.1030000@FreeBSD.org> References: <552E9132.6020604@FreeBSD.org>, <552E936A.1030000@FreeBSD.org> From: "Chris H" Subject: Re: perldoc is broken in 9, 10 and CURRENT with "xterm" TERM Date: Wed, 15 Apr 2015 10:04:43 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-perl@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: maintainer of a number of perl-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2015 17:03:39 -0000 On Wed, 15 Apr 2015 17:35:54 +0100 Matthew Seaman wrote > On 2015/04/15 17:26, Lev Serebryakov wrote: > > > > perldoc from perl 5.16 and perl 5.18 on 9, 10 and CURRENT shows ESC > > codes like this: > > > > "ESC[4mfieldsESC[24m") that do ESC[1mnot ESC[22minclude > > > > Terminal tried is "xterm" (PuTTY and cygwin's rxtv) and "cygwin" > > (cygwin's ssh from console). > > > > Adding screen or tmux in mix doesn't help, either. > > > > I've found closed PR, which explains or fixes nothing: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162463 > > As a workaround, add this to your environment: > > PERLDOC_PAGER='less -+C -E -R' This all seems so kludgy. In fact I ended up creating a port to remove the ANSI nonsense that shows up in the (type)script output generated by clang, in an effort to make it more readable. This stuff all seemed to show up about the time vt(4) did. Is there a coloration? ie; loader.conf(5) kern.vty=vt # current default kern.vty=sc # previous default Also given that the default .cshrc provides setenv PAGER more All of the suggested "fixes" just seem wrong, or more concisely; the proposed "fixes" cure the symptoms, but not the problem. What is the *actual* reason (cause)? Thanks. --Chris > > Cheers, > > Matthew