Re: strange behaviour of psql \e command - Mailing list pgsql-hackers

From Tom Lane
Subject Re: strange behaviour of psql \e command
Date
Msg-id 10325.1451668451@sss.pgh.pa.us
Whole thread Raw
In response to strange behaviour of psql \e command  (Oleg Bartunov <obartunov@gmail.com>)
Responses Re: strange behaviour of psql \e command  (Neil Tiffin <neilt@neiltiffin.com>)
List pgsql-hackers
Oleg Bartunov <obartunov@gmail.com> writes:
> I noticed, that psql's \e command doesn't worked for me complaining 'error
> opening file'. I did research and found that following setting in joe's (if
> I choose editor as joe) configuraton causes the problem:
> -exask         ^KX always confirms file name
> That worked for decades :), so I'm wondering what was changed either in El
> Capitan or psql code ?

I don't recall that we've changed anything much at all about \e recently,
so probably the way to bet is that the El Capitan update broke something
:-(.  Can anyone else confirm?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Some 9.5beta2 backend processes not terminating properly?
Next
From: Neil Tiffin
Date:
Subject: Re: strange behaviour of psql \e command