From: "Woolley, Rob" <rob.woolley@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: tom.zanussi@linux.intel.com, bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/3] knotty: Add automatic pager support
Date: Fri, 13 Mar 2015 15:41:37 -0400 [thread overview]
Message-ID: <55033D71.5070200@windriver.com> (raw)
In-Reply-To: <1426177814.9114.119.camel@linuxfoundation.org>
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.
Regards,
Rob
next prev parent reply other threads:[~2015-03-13 19:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 14:32 [PATCH 0/3] knotty: Add automatic pager support Rob Woolley
2015-02-27 14:32 ` [PATCH 1/3] knotty: Catch exceptions on broken pipes Rob Woolley
2015-02-27 14:32 ` [PATCH 2/3] knotty: Do not log show_versions output Rob Woolley
2015-02-27 14:32 ` [PATCH 3/3] knotty: Add automatic paging for bitbake -s and -e Rob Woolley
2015-03-12 15:25 ` [PATCH 0/3] knotty: Add automatic pager support Rob Woolley
2015-03-12 16:30 ` Richard Purdie
2015-03-13 19:41 ` Woolley, Rob [this message]
2015-03-13 21:12 ` Bernhard Reutner-Fischer
2015-03-13 21:37 ` Bernhard Reutner-Fischer
2015-03-17 15:05 ` Woolley, Rob
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55033D71.5070200@windriver.com \
--to=rob.woolley@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=tom.zanussi@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.