<div dir="ltr"><div>Given the change in behavior, should we also include changes to the documentation for the affected flags?<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 28, 2017 at 7:24 PM, Rob Woolley <span dir="ltr"><<a href="mailto:rob.woolley@windriver.com" target="_blank">rob.woolley@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The bitbake show_versions (-s) and show_environment (-e) commands provide<br>
a lot of non-interactive output. Even experienced users will sometimes<br>
forget to page the output.<br>
<br>
This enhancement adds a feature to automatically page these commands when<br>
using the knotty user interface. It doesn't affect any other commands<br>
and is designed to work in a similar fashion to the auto-paging in git.<br>
<br>
This was tested with bitbake -s and bitbake -s | less (and -e) to ensure that<br>
there were no regressions. This includes testing broken pipe conditions<br>
caused by quitting the pager before the full output has been sent through<br>
the pipe.<br>
<br>
This is an update of my previous patch from February 2015 and adds support<br>
for Python 3 and utf-8.<br>
<br>
PATCH v1: <a href="https://patchwork.openembedded.org/patch/89543/" rel="noreferrer" target="_blank">https://patchwork.<wbr>openembedded.org/patch/89543/</a><br>
YOCTO #9203: <a href="https://bugzilla.yoctoproject.org/show_bug.cgi?id=9203" rel="noreferrer" target="_blank">https://bugzilla.yoctoproject.<wbr>org/show_bug.cgi?id=9203</a><br>
</blockquote></div><br></div>