Re: tab-completion for \lo_import

Lists: pgsql-hackers
From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: tab-completion for \lo_import
Date: 2013-07-10 15:28:32
Message-ID: CAK3UJRF8B2kB0KVNAavA8OyL3OtYz=n0zO549tCEziqGdJcKsg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi all,
Is there any reason not to tab-complete the local filename used by the
\lo_import command? Small patch to do so attached.
Josh

Attachment Content-Type Size
tab_complete_lo_import.diff application/octet-stream 923 bytes

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tab-completion for \lo_import
Date: 2013-07-15 18:29:46
Message-ID: CA+TgmobXZau9hfEukNX2FrGzRSQXVRAUpuzUMie46m0shSR02g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Wed, Jul 10, 2013 at 11:28 AM, Josh Kupershmidt <schmiddy(at)gmail(dot)com> wrote:
> Is there any reason not to tab-complete the local filename used by the
> \lo_import command? Small patch to do so attached.

Looks good to me. Committed.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company