9203 2016-03-03 09:36:57 +0000 Automatically paginate bitbake -e output 2021-06-17 15:23:42 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 2.2 x86 Multiple RESOLVED WONTFIX Low enhancement Future 1 joshuagloe unassigned libertad.gonzalez.de.la.cruz poky.bs.watcher poky.watcher randy.macleod richard.purdie ross.burton --- --- Don't know oldest_to_newest 59661 0 joshuagloe 2016-03-03 09:36:57 +0000 Git automatically uses a pager (less, by default) to paginate certain subcommands with long output — we should consider adding this feature to bitbake and using it for -e and possibly -S 74353 1 garbados 2017-06-19 21:58:26 +0000 If I understand correctly, this issue says that: - `bitbake -e` should use a pager like less, such that it resembles `bitbake -e | less` - make the pager configurable, so you can use something besides less. - `bitbake -S` should also use a configurable pager? What environment variables should be used to determine the pager? 74365 2 ross.burton 2017-06-20 10:06:38 +0000 The standard variable is "PAGER". 74558 3 garbados 2017-06-26 23:39:14 +0000 There's been some pushback about building pager support into bitbake, in favor of retaining the current approach of allowing the user to pipe to a paginator themselves. And there seems to be a precedent on pagination: http://lists.openembedded.org/pipermail/bitbake-devel/2015-March/005545.html Are we sure this is a feature we want? 90690 4 richard.purdie 2021-06-17 15:23:42 +0000 git is mostly a non-interactive command, bitbake is different in that it can be longer running and interactive (e.g. knotty). I think having the user use a pager as/when necessary isn't too much of a hardship and avoids a ton of potential pitfalls.