Re: failure of \e in psql

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: failure of \e in psql
Date: 1999-11-11 21:51:14
Message-ID: 199911112151.QAA16058@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 1999-11-11, Bruce Momjian mentioned:
>
> > I see that \e no longer works as expected:
> >
> > test=> select * from pg_class;
> > ...
> > test=> \e
> >
> > and in the editor, the query is not appearing. The 'select' query
> > should appear in the editor because I have not entered a non-backslash
> > command to clear the query buffer.
>
> Well, once you send it, it's sent and gone. You have to edit it before you
> send it. I guess I'm not following you. Of course you should somehow be
> able to re-edit the previous query. Hmm.

That is how it used to work. You run the query, get an error, and \e
pulls it into the editor for fixing.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-11-11 21:56:36 Re: [HACKERS] Slow - grindingly slow - query
Previous Message Bruce Momjian 1999-11-11 21:50:18 Re: psql and \p\g