Casey Allen Shobe writes:
> Can tab completion be disabled without disabling command line history? I
> noticed -n disables both. I would gladly trade tab completion for tab
> pastability, but I rely heavily on command line history.
man psql, search for "disable"
Also, you might find it easier
> Can tab completion be disabled without disabling command line history? I
> noticed -n disables both. I would gladly trade tab completion for tab
> pastability, but I rely heavily on command line history.
Perhaps annoying, but a simple work around is to use
Formats like tab in the code, b
The problem is that most items in postgresql are tab completed.
Cut and past your text into a bash or zsh prompt. It injects a bunch of
filenames into your data, as per tab completion.
Annoying, but for the benefits it's livable.
Perhaps a toggle could be created to disable tab completion?
O
Casey Allen Shobe <[EMAIL PROTECTED]> writes:
> Can tab completion be disabled without disabling command line history?
Get out the readline man page. I believe you can configure it six
ways from Sunday, but I've never tried myself ...
regards, tom lane
-
On Tuesday 27 August 2002 01:48 am, Tom Lane wrote:
> Turn off readline (psql -n). For someone accustomed to tab completion,
> the above is about as sensible as demanding we disable backspace.
Right, my original build of postgres did not have tab completion support as I
did not have readline (a
Casey Allen Shobe <[EMAIL PROTECTED]> writes:
> Tabs should paste; they're normal characters.
Turn off readline (psql -n). For someone accustomed to tab completion,
the above is about as sensible as demanding we disable backspace.
It would be nice if we could distinguish pasted tabs from manual
Let's say I have typed a nice formatted SQL statement like so:
select b1.blah,
b1.blah2,
b2.blah3
fromblah_table as b1
inner join only blah_table2 as b2
on b1.blah = b2.blah;
...using tabs as the indenting medium. Now I copy that
