Re: Terminal width for help output - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Terminal width for help output
Date
Msg-id 200711152111.lAFLBlC06103@momjian.us
Whole thread Raw
In response to Re: Terminal width for help output  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
Joshua D. Drake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Thu, 15 Nov 2007 16:04:46 -0500
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> > Peter Eisentraut <peter_e@gmx.net> writes:
> > > Do we care to maintain a maximum width for programs' --help output
> > > (and psql's \?)?  I think 79 characters was once a recommendation
> > > (or perhaps 72), but we have a couple of violations either way,
> > > which I'd like to fix, but what to?
> > 
> > I think 79 is still a reasonable maximum.  AFAIK 80 columns is still a
> > pretty standard terminal window width, but if you try to print in the
> > last column you may get unexpected extra blank lines.
> 
> O.k. this might be offtopic if it is feel free to smack me... but I
> have noticed that psql really breaks on terminals that are wide.. \df
> works fine, but \df+ is completely broke.
> 
> Can't we just ask the terminal?

Peter is talking about --help text that is hard-coded into the binary,
meaning you don't run it through some filter before output.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Terminal width for help output
Next
From: Dave Page
Date:
Subject: [Fwd: PGBuildfarm member narwhal Branch HEAD Status changed from OK to Make failure]