Re: Several problems in tab-completions for SET/RESET

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Several problems in tab-completions for SET/RESET
Date: 2016-02-01 13:22:31
Message-ID: CAHGQGwGANT0dt_UE+vjco_fE3wQL6AhKOtLaTxVyt8K9jkuqVA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 1, 2016 at 9:23 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Mon, Feb 1, 2016 at 9:15 PM, Fujii Masao wrote:
>> If we do that, we also should change the tab-completion for SET command
>> so that "=" is suggested. But I'm afraid that which might decrease that
>> tab-completion.
>>
>> Imagine the case of "SET work_mem <tab>". If "TO" and "=" are suggested,
>> we need to type either "T" or "=" and then <tab> to input the setting value.
>> Otherwise, "SET work_mem <tab>" suggests only "TO" and we can input
>> the setting value by just typing <tab> again.
>> This extra step is very small, but SET command is usually used very often,
>> so I'd like to avoid such extra step.
>
> OK, that's fine.

Pushed. Thanks!

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2016-02-01 13:27:35 Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs)
Previous Message Fujii Masao 2016-02-01 13:08:09 Re: Fwd: [DOCS] pgbench doc typos