All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Woolley, Rob" <rob.woolley@windriver.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
	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: Tue, 17 Mar 2015 11:05:19 -0400	[thread overview]
Message-ID: <550842AF.2090003@windriver.com> (raw)
In-Reply-To: <471B1967-EB47-4869-98B6-9A0750147888@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]



On 3/13/2015 5:37 PM, Bernhard Reutner-Fischer wrote:
> On March 13, 2015 10:12:00 PM GMT+01:00, Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> wrote:
>> On March 13, 2015 8:41:37 PM GMT+01:00, "Woolley, Rob"
>> <rob.woolley@windriver.com> wrote:
>>> On 03/12/2015 12:30 PM, Richard Purdie wrote:
>>>
>>>> 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.
> PS:
> http://comments.gmane.org/gmane.comp.version-control.patchwork/1144
> ;)

Thanks for the feedback, Bernhard.

I set defaults for LESS and LV based on what git does for its automatic 
paging:
https://github.com/git/git/blob/master/pager.c#L77 
<https://github.com/git/git/blob/master/pager.c#L57>

The part with cat is also inspired by git:
https://github.com/git/git/blob/master/pager.c#L51 
<https://github.com/git/git/blob/master/pager.c#L34>
<https://github.com/git/git/blob/master/pager.c#L57>
I see the first 2 patches went in.  I'm going to give the automatic 
paging patch some more soak time.

If anyone is interested in trying it out, I've created a gist for it here:
https://gist.github.com/rcwoolley/c662b8e1494c58b1a24d

Regards,
Rob

[-- Attachment #2: Type: text/html, Size: 3676 bytes --]

      reply	other threads:[~2015-03-17 15:05 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
2015-03-13 21:12       ` Bernhard Reutner-Fischer
2015-03-13 21:37         ` Bernhard Reutner-Fischer
2015-03-17 15:05           ` Woolley, Rob [this message]

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=550842AF.2090003@windriver.com \
    --to=rob.woolley@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=rep.dot.nop@gmail.com \
    --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.