Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Rob Woolley <rob.woolley@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/3] knotty: Add automatic pager support
Date: Fri, 27 Feb 2015 09:32:21 -0500	[thread overview]
Message-ID: <1425047544-4820-1-git-send-email-rob.woolley@windriver.com> (raw)

The bitbake show_versions (-s) and show_environment (-e) commands provide
a lot of non-interactive output.  Even experienced users will sometimes
forget to page the output.

This series adds a feature to automatically page these commands when
using the knotty user interface.  It doesn't affect any other commands
and is designed to work in a similar fashion to the auto-paging in git.

This was tested with bitbake -s and bitbake -s | less (and -e) to ensure that
there were no regressions.  This includes testing broken pipe conditions
caused by quitting the pager before the full output has been sent through
the pipe.

knotty: Catch exceptions on broken pipes
 lib/bb/ui/knotty.py |   43 ++++++++++++++++++++++++-------------------
 1 file changed, 24 insertions(+), 19 deletions(-)

knotty: Do not log show_versions output
 lib/bb/ui/knotty.py |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

knotty: Add automatic paging for bitbake -s and -e
 lib/bb/ui/knotty.py |   46 +++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 43 insertions(+), 3 deletions(-)


             reply	other threads:[~2015-02-27 14:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 14:32 Rob Woolley [this message]
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
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=1425047544-4820-1-git-send-email-rob.woolley@windriver.com \
    --to=rob.woolley@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox