On (15/03/18 22:32), Erik Christiansen put forth the
proposition:
On 14.03.18 23:23, David Woodfall wrote:
On (14/03/18 16:01), Ian Zimmerman put forth the
proposition:
> On 2018-03-14 13:13, David Woodfall wrote:
>
> > > Previously, I used elinks and it works fine with autoview, however
> >
On 14.03.18 23:23, David Woodfall wrote:
> On (14/03/18 16:01), Ian Zimmerman put forth the
> proposition:
> > On 2018-03-14 13:13, David Woodfall wrote:
> >
> > > > Previously, I used elinks and it works fine with autoview, however
> > > > when I try to pipe to it it also renders the headers in
On (14/03/18 23:23), Dave Woodfall put forth the
proposition:
On (14/03/18 16:01), Ian Zimmerman put forth the
proposition:
On 2018-03-14 13:13, David Woodfall wrote:
Previously, I used elinks and it works fine with autoview, however
when I try to pipe to it it also renders the headers ins
On (14/03/18 16:01), Ian Zimmerman put forth the
proposition:
On 2018-03-14 13:13, David Woodfall wrote:
> Previously, I used elinks and it works fine with autoview, however
> when I try to pipe to it it also renders the headers instead of just
> the body.
When you try a pipe, is that pipin
On 2018-03-14 13:13, David Woodfall wrote:
> > Previously, I used elinks and it works fine with autoview, however
> > when I try to pipe to it it also renders the headers instead of just
> > the body.
When you try a pipe, is that piping the message (as a pipe command would
do in the index view) o
On (14/03/18 12:53), Dave Woodfall put forth the
proposition:
I've just found reason to not autoview HTML and to do it manually with
a bind.
Previously, I used elinks and it works fine with autoview, however
when I try to pipe to it it also renders the headers instead of just
the body.
This i
