Hi Ingo,
In article <20180329235743.ge59...@athene.usta.de> Ingo Schwarze
wrote:
> > Can I do anything to fix this?
>
> Yes.
>
I've always wondered why groff did that nonsense with man pages. I
remember discussing this same issue in groff mailing lists years ago
(with E.
> Don't you already need this logic, getenv(3) + isatty(3), to decide if
> you use a pager or not? Although I don't understand why getenv(3) is
> needed, isn't a TIOCGWINSZ ioctl(2) enough?.
Because there is a defacto standard that some SVR2 environment (before
the ioctl) be honoured by many
On 3/31/18, Andras Farkas wrote:
> On Fri, Mar 30, 2018 at 11:23 AM, Chris Bennett wrote:
>> This is very important. Our brains just are not good at working with
>> long lines. This is hard-wired. If anyone doesn't believe me, try
>> setting your browser window to a narrower width or use reader
On Fri, Mar 30, 2018 at 01:57:43AM +0200, Ingo Schwarze wrote:
> I do *NOT* want to add SIGWINCH signal handling to man(1) to abort
> less(1), reformat, and respawn less(1) in that case. That kind of
> magic would be over the top, and SIGWINCH is an abomination in the
> first place.
Why on earth
On Fri, Mar 30, 2018 at 11:23 AM, Chris Bennett
wrote:
> This is very important. Our brains just are not good at working with
> long lines. This is hard-wired. If anyone doesn't believe me, try
> setting your browser window to a narrower width or use reader mode.
On 31/03/18(Sat) 03:20, Ingo Schwarze wrote:
> Paul Irofti wrote on Fri, Mar 30, 2018 at 11:23:54AM +0300:
> [...]
> > which is EXACTLY what I was looking for! Can it be the default? :)
>
> I'm neither particularly enthusiastiastic (because it requires
> more code, in particular more getenv(3)
Hi Paul,
Paul Irofti wrote on Fri, Mar 30, 2018 at 11:23:54AM +0300:
> Ingo Schwarze wrote:
>> * Nowadays, i guess that terminals narrower than 80 columns
>>have become seriously rare, so there is not very widespread
>>benefit for that case.
> Maybe that was true when we still had 4:3
Fri, 30 Mar 2018 08:23:12 -0700 Chris Bennett
> On Thu, Mar 29, 2018 at 11:57:43PM +, Ingo Schwarze wrote:
> > I *could* maybe teach man(1) to honour $COLUMN by default when
> > starting up in interactive mode, but i did not do so for the following
> >
On Thu, Mar 29, 2018 at 11:57:43PM +, Ingo Schwarze wrote:
> I *could* maybe teach man(1) to honour $COLUMN by default when
> starting up in interactive mode, but i did not do so for the following
> reasons:
>
> * Many people are using terminals wider than 80 columns, but
>texts get hard
On Fri, Mar 30, 2018 at 01:57:43AM +0200, Ingo Schwarze wrote:
> When you want a manpage to exactly fill the available terminal width,
> you can use an alias like this:
>
> $ alias wman='man -Owidth=$COLUMNS'# or
> $ alias wman='man -Owidth=$((COLUMNS-2))'
>
> Of course, if you
Hi Ingo,
Thanks for the detailed reply. I was expecting it :)
> * Nowadays, i guess that terminals narrower than 80 columns
>have become seriously rare, so there is not very widespread
>benefit for that case.
Maybe that was true when we still had 4:3 screens, but now I always
have 2 or
On Fri, Mar 30, 2018 at 01:57:43AM +0200, Ingo Schwarze wrote:
> Hi Paul,
>
> Theo de Raadt wrote on Thu, Mar 29, 2018 at 04:17:14PM -0600:
> > piroft@ wrote:
>
> >> Is there any reason why manpage text does not resize nicely
> >> with <80 columns xterms?
>
> I want to avoid excessive magic.
>
Hi Paul,
Theo de Raadt wrote on Thu, Mar 29, 2018 at 04:17:14PM -0600:
> piroft@ wrote:
>> Is there any reason why manpage text does not resize nicely
>> with <80 columns xterms?
I want to avoid excessive magic.
By the way, actually, the default width is 78, not 80.
By tradition.
>> Is it
> Is there any reason why manpage text does not resize nicely with <80
> columns xterms? Is it because of less(1)? Can I do anything to fix this?
It is pre-formatted.
Hi,
Is there any reason why manpage text does not resize nicely with <80
columns xterms? Is it because of less(1)? Can I do anything to fix this?
Thanks,
Paul
15 matches
Mail list logo