Bruce Momjian wrote: <snip>
Wouldn't it depend on how this gets implemented?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?
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
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
