Re: Two successive tabs in test case are causing syntax error in psql

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jingtang Zhang <mrdrivingduck(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Two successive tabs in test case are causing syntax error in psql
Date: 2022-07-10 15:26:18
Message-ID: 20220710152618.2mi5siezhqdpsz3y@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022-Jul-08, Tom Lane wrote:

> The usual recommendation for pasting text into psql when it contains
> tabs is to start psql with the -n switch to disable tab completion.

"Bracketed paste" also solves this problem. To enable this feature,
just edit your $HOME/.inputrc file to have the line
set enable-bracketed-paste on
(then restart psql) which will cause the text passed to be used
literally, so the tabs won't invoke tab-completion. There are other
side-effects: if you paste a multi-command string, the whole string is
added as a single entry in the history rather than being separate
entries. I find this extremely useful; there are also claims of this
being more secure.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2022-07-10 15:32:55 Re: Cleaning up historical portability baggage
Previous Message Greg Stark 2022-07-10 15:25:40 Re: Cleaning up historical portability baggage