Re: strange behaviour of psql \e command

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: obartunov(at)gmail(dot)com
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: strange behaviour of psql \e command
Date: 2016-01-01 17:14:11
Message-ID: 10325.1451668451@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Oleg Bartunov <obartunov(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Tiffin 2016-01-01 18:23:50 Re: strange behaviour of psql \e command
Previous Message Amit Kapila 2016-01-01 12:41:33 Re: Some 9.5beta2 backend processes not terminating properly?