From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | David Fetter <david(at)fetter(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Uppercase tab completion keywords in psql? |
Date: | 2012-05-04 17:46:28 |
Message-ID: | 1336153588.9886.3.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On tor, 2012-05-03 at 15:47 -0400, Bruce Momjian wrote:
> Peter, where are we on this?
I hadn't received any clear feedback, but if no one objects, I can
commit it.
> ---------------------------------------------------------------------------
>
> On Fri, Mar 30, 2012 at 08:16:59PM +0300, Peter Eisentraut wrote:
> > On fre, 2012-03-23 at 07:52 -0700, David Fetter wrote:
> > > On Thu, Mar 22, 2012 at 06:05:30PM -0400, Andrew Dunstan wrote:
> > > > 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?
> > >
> > > Something like (upper|lower|preserve) ?
> >
> > How about this patch then? (There are actually four possible settings,
> > see patch.)
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Urbański | 2012-05-04 18:00:55 | Re: PL/Python result set slicing broken in Python 3 |
Previous Message | Peter Eisentraut | 2012-05-04 17:45:10 | Re: remove dead ports? |