Re: Uppercase tab completion keywords in psql?

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: David Fetter <david@fetter.org>, Andrew Dunstan <andrew@dunslane.net>, PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Date: 2012-05-05T13:03:38Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. psql: Add variable to control keyword case in tab completion

  2. psql: Case preserving completion of SQL key words

On Fri, May 04, 2012 at 08:46:28PM +0300, Peter Eisentraut wrote:
> 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.

I think there were enough people that wanted some kind of control in
this area.  I did give you feedback on the patch.

---------------------------------------------------------------------------

> > 
> > 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.)
> 
> 

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +