Re: Return of "can't paste into psql" issue - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Return of "can't paste into psql" issue
Date
Msg-id CAHyXU0wjNPvG=OrGf0EY1yRY0Pc8OUq6LY-B_J7G+VDTf+nNEw@mail.gmail.com
Whole thread Raw
In response to Re: Return of "can't paste into psql" issue  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: Return of "can't paste into psql" issue
List pgsql-hackers
On Wed, Jul 17, 2013 at 6:30 PM, Dimitri Fontaine
<dimitri@2ndquadrant.fr> wrote:
> Josh Berkus <josh@agliodbs.com> writes:
>> So, an even more practical workaround (I've been using cat | psql), but
>> still a mysterious issue.
>
> As a workaround you might try \e with EDITOR=emacs or some of the other
> solutions you've been pasting, maybe even cat, so that you can switch
> that readline-completion-bug-free environment for just that paste?

Well, I use \e=vim and it works fine.  But, sometimes you forget and
the results can be destructive to the database. I messed around for a
little bit with the tab completion callback routine yesterday and I
now believe that's not the issue.  It only fires when you tab AFAICT
-- so the problem is in the readline function itself which reduces the
set of solutions somewhat -- either you run it or you don't.

One thing that could solve a lot of issues would be to disable
readline when inside a dollar quote etc.

merlin



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: getting rid of SnapshotNow
Next
From: Merlin Moncure
Date:
Subject: Re: Return of "can't paste into psql" issue