Re: Command-line client sometimes misinterprets tabs for nulls

Поиск
Список
Период
Сортировка
От Casey Allen Shobe
Тема Re: Command-line client sometimes misinterprets tabs for nulls
Дата
Msg-id 200208280101.51899.cshobe@secureworks.net
обсуждение исходный текст
Ответ на Re: Command-line client sometimes misinterprets tabs for nulls  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Command-line client sometimes misinterprets tabs for nulls  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Command-line client sometimes misinterprets tabs for  (Rod Taylor <rbt@zort.ca>)
Re: Command-line client sometimes misinterprets tabs for  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-bugs
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=20
did not have readline (a notice at the end of the configure script would ha=
ve=20
been nice, maybe a summary of what will and won't be supported?).  However,=
 I=20
love the command-line history, so readline was a must ;).

> It would be nice if we could distinguish pasted tabs from manually-typed
> tabs, but I'm not aware of any way that psql could tell the difference.

Can tab completion be disabled without disabling command line history?  I=
=20
noticed -n disables both.  I would gladly trade tab completion for tab=20
pastability, but I rely heavily on command line history.

Thanks,

--=20
Casey Allen Shobe / Network Security Analyst & PHP Developer
SecureWorks, Inc. / 404.327.6339 x169 / Fax: 404.728.0144
cshobe@secureworks.net / http://www.secureworks.net
Content is my own and does not necessarily represent my company.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Bruno Wolff III
Дата:
Сообщение: Potential buffer overflow in contrib/cube/cubeparse.y
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Command-line client sometimes misinterprets tabs for nulls