From owner-freebsd-questions@FreeBSD.ORG Wed Dec 17 13:33:58 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E6F9EFD2 for ; Wed, 17 Dec 2014 13:33:58 +0000 (UTC) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.229]) by mx1.freebsd.org (Postfix) with ESMTP id A6F17CC1 for ; Wed, 17 Dec 2014 13:33:58 +0000 (UTC) Received: from [204.210.114.114] ([204.210.114.114:42776] helo=localhost.hawaii.res.rr.com) by dnvrco-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 4D/DC-31058-F3681945; Wed, 17 Dec 2014 13:33:51 +0000 Received: by localhost.hawaii.res.rr.com (Postfix, from userid 1000) id 5EEAA5CD0; Wed, 17 Dec 2014 03:38:08 -1000 (HST) Date: Wed, 17 Dec 2014 03:38:08 -1000 From: parv@pair.com To: nvass@gmx.com Subject: Re: A pager with explicit (un)wrap-long-lines key bindings and/or options Message-ID: <20141217133808.GA91842@holstein.holy.cow> Mail-Followup-To: nvass@gmx.com, f-q MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <549175FC.2070703@gmx.com> X-RR-Connecting-IP: 107.14.64.130:25 X-Authority-Analysis: v=2.1 cv=Bq0TwOn5 c=1 sm=1 tr=0 a=lLOF/jpPrR0dcgWXP1EvZg==:117 a=lLOF/jpPrR0dcgWXP1EvZg==:17 a=ayC55rCoAAAA:8 a=kj9zAlcOel0A:10 a=Ymsr-CWnAAAA:8 a=A92cGCtB03wA:10 a=uPZiAMpXAAAA:8 a=hSLGs5F87yaBtGYIgw0A:9 a=CjuIK1q_8ugA:10 X-Cloudmark-Score: 0 Cc: f-q X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Dec 2014 13:33:59 -0000 Nikos wrote on Wed Dec 17 12:24:38 UTC 2014 ... > > in message <20141217120919.GA91144@holstein.holy.cow>, > wrote parv@p thusly... > > > > I am looking for a pager that has EXPLICIT options and/or key bindings > > (preferred) to set & unset wrapping of long lines[0]. > ... > > Environment variable, LESS, is set to "-SsIXR -x4"[1]. less has > > only a option to now wrap long lines (-S | --chop-long-lines). > > Listed in the manual page is that default is not to wrap. (Well, > > invoking less as "\less" does not override the "-S" in LESS.) > ... > > [1] As to obvious reason to not set "-S" in LESS: setting the -S > > option is helpful most of the time where seeing extra > > characters can be deferred. > > While less is running, you can switch from chop to fold and > reversely by pressing -S. Is this what you want? Oh, yes! Exactly that behaviour is what I had wanted. Thanks, Nikos. That reminded me to re-read the option modification section, in particular ... -+ Followed by one of the command line option letters this will reset the option to its default setting and print a message describing the new setting. (The "-+X" command does the same thing as "-+X" on the command line.) This does not work for string-valued options. ... -! Followed by one of the command line option letters, this will reset the option to the "opposite" of its default setting and print a message describing the new setting. This does not work for numeric or string-valued options. ... so sending text to "less -+S" via pipe worked as expected. And, that stalled the creation of vi(m)-as-pager until some later date. To that end ... Pipe Vim buffer to stdout http://stackoverflow.com/questions/10686183/pipe-vim-buffer-to-stdout --