From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | psql case preserving completion |
Date: | 2012-01-11 20:29:18 |
Message-ID: | 1326313758.22276.12.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
In psql, the tab completion always converts key words to upper case. In
practice, I and I think most users type in lower case. So then you end
up with commands looking like this:
=> alter TABLE foo add CONSTRAINT bar check (a > 0);
To address this, I have implemented a slightly different completion mode
that looks at the word being completed and converts the completed word
to the case of the original word. (Well, it looks at the first letter.)
In fact, since almost all completions in psql are of this nature, I made
this the default mode for COMPLETE_WITH_CONST and COMPLETE_WITH_LIST and
added a new macro COMPLETE_WITH_LIST_CS that uses the old case-sensitive
behavior. The latter is used mainly for completing backslash commands.
After playing with this a little, I find the behavior more pleasing.
Less yelling. ;-)
Patch attached.
Attachment | Content-Type | Size |
---|---|---|
psql-cp-completion.patch | text/x-patch | 4.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2012-01-11 20:35:03 | Re: psql case preserving completion |
Previous Message | Alvaro Herrera | 2012-01-11 20:16:00 | Re: PL/Python result metadata |