Re: [HACKERS] Autocomplete <TAB> on Postgres7.4beta5 not working?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ian Barwick <barwick(at)gmx(dot)net>
Cc: Alvaro Herrera Munoz <alvherre(at)dcc(dot)uchile(dot)cl>, Gaetano Mendola <mendola(at)bigfoot(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Autocomplete <TAB> on Postgres7.4beta5 not working?
Date: 2003-10-28 23:45:49
Message-ID: 29601.1067384749@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Ian Barwick <barwick(at)gmx(dot)net> writes:
> On Tuesday 28 October 2003 23:47, Tom Lane wrote:
>> Another odd thing was that after completing "pg_catalog.", it
>> wouldn't go any further --- one must type "p" here, even though all the
>> possible completions begin "pg_". (Possibly that could be fixed, but
>> I don't know readline's behavior well enough to be sure.)

> I'm not sure whether it's intended or not, but explicitly adding
> pg_catalog to the search path alleviates this.

It turns out that I unintentionally broke that a few days ago while
adding quote_ident() calls. I've repaired that damage, so now you can
go
pg_c<TAB><TAB>
and get
pg_catalog.pg_
which is one less keystroke than I claimed before. I still think it's
too many though ...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2003-10-28 23:49:28 Re: [HACKERS] Autocomplete <TAB> on Postgres7.4beta5 not working?
Previous Message Rod Taylor 2003-10-28 23:22:41 Re: [HACKERS] Autocomplete <TAB> on Postgres7.4beta5 not working?

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-10-28 23:49:28 Re: [HACKERS] Autocomplete <TAB> on Postgres7.4beta5 not working?
Previous Message Rod Taylor 2003-10-28 23:22:41 Re: [HACKERS] Autocomplete <TAB> on Postgres7.4beta5 not working?