Re: psql SET/RESET/SHOW tab completion

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql SET/RESET/SHOW tab completion
Date: 2005-08-14 01:42:45
Message-ID: 87vf298fai.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-08-14 03:06:38 Re: PATCH to allow concurrent VACUUMs to not lock each
Previous Message Alvaro Herrera 2005-08-14 01:37:13 Re: DROP OWNED BY