Re: psql SET/RESET/SHOW tab completion - Mailing list pgsql-hackers

From Greg Stark
Subject Re: psql SET/RESET/SHOW tab completion
Date
Msg-id 87vf298fai.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: psql SET/RESET/SHOW tab completion  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: psql SET/RESET/SHOW tab completion  (Dawid Kuroczko <qnex42@gmail.com>)
Re: psql SET/RESET/SHOW tab completion  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:

> However, if you favor a "no thought required" approach, listing 'em
> all is certainly the path of least resistance.  I'm just dubious that
> that maximizes the usefulness of tab completion.

I'm not sure if you're interested, but my 2c speaking as a user would be for
tab completion to include all variables. I often hit tab completion in new
programs just to find out what's out there and would take something missing to
be positive proof it didn't exist.

-- 
greg



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: DROP OWNED BY
Next
From: Bruce Momjian
Date:
Subject: pg_stat_file() and length/size