| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: Uppercase tab completion keywords in psql? |
| Date: | 2012-03-23 14:51:16 |
| Message-ID: | 1332514224-sup-4461@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Andrew Dunstan's message of jue mar 22 19:05:30 -0300 2012:
>
> On 03/22/2012 05:49 PM, Bruce Momjian wrote:
> >
> > Robert Haas and I are disappointed by this change. I liked the fact
> > that I could post nice-looking SQL queries without having to use my
> > capslock key (which I use as a second control key). Any chance of
> > reverting this change?
> >
>
> Should it be governed by a setting?
A \set variable perhaps? +1 Would the old behavior be the default?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2012-03-23 14:52:00 | Re: Uppercase tab completion keywords in psql? |
| Previous Message | Alvaro Herrera | 2012-03-23 14:30:04 | Re: Finer Extension dependencies |