On Tue, Oct 02, 2018 at 04:48:30AM +0200, Guillem Jover wrote:
> > This is exactly the opposite of how unix programs should behave - stdout
> > goes to a tty unless redirected. If a user **wants** to view the output of
> > a program in a pager, then they can pipe it to less or whatever themselves.
Hi,
Guillem Jover wrote:
> So, first, thanks for the constructive proposals! But I'd rather not
> revert this change. I'm happy to implement anything sane people might
> find useful to cope with such change. This includes the following
> changes which I've started coding:
>
> * DPKG_PAGER (equi
hi,
On Tue, Oct 02, 2018 at 04:48:30AM +0200, Guillem Jover wrote:
> This includes the following
> changes which I've started coding:
>
> * DPKG_PAGER (equivalent to PAGER, so it will accept arguments).
> * Set LESS (if unset) to something along the lines of -FRSXMQ, which
> sould fix the
Hi!
On Fri, 2018-09-28 at 02:42:19 +1000, Craig Sanders wrote:
> Package: dpkg
> Version: 1.19.1
> This is exactly the opposite of how unix programs should behave - stdout
> goes to a tty unless redirected. If a user **wants** to view the output of
> a program in a pager, then they can pipe it t
On Fri, Sep 28, 2018 at 02:42:19AM +1000, Craig Sanders wrote:
> I upgraded dpkg today and noticed that 'dpkg -l' now always pipes its output
> through less, even if $PAGER is unset. The only way to get the output to go
> to the tty is to explicitly pipe it to cat.
>
> This is exactly the opposit
Package: dpkg
Version: 1.19.1
I upgraded dpkg today and noticed that 'dpkg -l' now always pipes its output
through less, even if $PAGER is unset. The only way to get the output to go
to the tty is to explicitly pipe it to cat.
This is exactly the opposite of how unix programs should behave - std
6 matches
Mail list logo