| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Justin Clift <justin(at)postgresql(dot)org> |
| Cc: | Dan Langille <dan(at)langille(dot)org>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql and readline |
| Date: | 2003-01-09 15:05:15 |
| Message-ID: | 200301091505.h09F5Fl09065@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Justin Clift wrote:
> Dan Langille wrote:
> <snip>
> > As this is changing existing behaviour, I think adding an optional
> > switch to revert to the old behaviour is a good idea.
>
> Two thoughts:
>
> a) Is it possible to change the behavior of the history as we're
> discussing? Haven't heard Peter's response to this.
>
> b) Do we really want to go to the effort of adding a switch to revert to
> previous behaviour for something like this? It's almost definitely a
> win to have \e commands appear in the history, and seems a bit to
> trivial for adding switches for.
Let's suppose I am writing a query, and then I do \e to edit the query,
and I exit the editor and return to psql. Suppose I decide I want to
reedit, so I up arrow. I would expect to get \e, not the query I just
edited, no?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2003-01-09 15:12:29 | Re: psql and readline |
| Previous Message | Tom Lane | 2003-01-09 15:04:14 | Re: [HACKERS] PostgreSQL libraries - PThread Support, but not use... |