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.) >
Yes, very nice. I found the "preserve" modes confusing, but I see the problem that saying "preserve" doesn't tell us how to expand a word where we didn't type anything. > + Determines which letter case to use when completing an SQL key word. > + If set to <literal>lower</literal> or <literal>upper</literal>, the > + completed word will be in lower or upper case, respectively. If set > + to <literal>preserve-lower</literal> > + or <literal>preserve-upper</literal> (the default), the completed > word > + will be in the case of the word already entered, but words being ----- The "being" word above got me confused; I would remove it. > + completed without anything entered will be in lower or upper case, > + respectively. "without anything" -> "with nothing" ? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers