Обсуждение: strange behaviour of psql \e command

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

> On Jan 1, 2016, at 11:14 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> 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?
>

Seems to work fine for me with vi on OS X 10.11.2 (15C50) and VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2015
16:22:14)Compiled by root@apple.com 

Nell