From: | Justin Clift <justin(at)postgresql(dot)org> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
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:12:29 |
Message-ID: | 3E1D915D.7040900@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
<snip>
> 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?
Wouldn't it depend on how this gets implemented?
Maybe least negative impact approach (suggested already): If the "large
command that was edited" is put in the command history before the \e,
then both are available and there is no big change from "expected
behaviour".
i.e. one up arrow get the previous \e, and a second up arrow would bring
up the command that was worked upon.
?
Regards and best wishes,
Justin Clift
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-01-09 15:13:14 | Re: psql and readline |
Previous Message | Bruce Momjian | 2003-01-09 15:05:15 | Re: psql and readline |