[bitbake-devel] [PATCH 0/3] knotty: Add automatic pager support

[Bernhard Reutner-Fischer]

On March 13, 2015 8:41:37 PM GMT+01:00, "Woolley, Rob" <rob.woolley at windriver.com> wrote:
>
>On 03/12/2015 12:30 PM, Richard Purdie wrote:
>> On Thu, 2015-03-12 at 11:25 -0400, Rob Woolley wrote:
>>> Hi,
>>>
>>> Just wanted to send out a ping to see if this enhancement is
>desired.
>>>
>>> It scratches an itch for me, but not sure how others feel about it.
>>>
>>> If there are any changes I can make or extra tests I can run, please
>let
>>> me know.
>> Patches 1/2 look good, I've run into the EPIPE issue myself and I
>have
>> noticed the crazy logfile so those can likely be merged.
>>
>> I'm less sure about 3, letting the user pipe the output to less when
>> needed would seem to be the better way to have this rather than
>adding
>> in specific pagination support?
>>
>> Cheers,
>>
>> Richard
>Sounds cool.  The exception was bugging me, so I'm glad to hear those 
>ones look good.
>
>As far as the 3rd patch is concerned: I remember when I first used 
>bitbake, I was surprised by the flood of data coming from those 
>options.  I would suggest that doing the automatic paging provides a 
>better first impression and saves unnecessary typing.
>
>I noticed that lib/image/help.py and lib/bsp/help.py have auto-paging 
>for the help command.  I've CC'd Tom Zanussi for his opinion.

Using PAGER is a good thing IMO.
Not so setting LESS or LV nor outsmarting users PAGER=cat nor defaulting to less.
I would also not attempt to check access() et al, just let the user fix her eventually broken export.

YMMV.
HTH && cheers,