On 9 Jan 2003 at 10:13, Bruce Momjian wrote:

> Justin Clift wrote:
> > 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.
> Makese sense.  However, it still has the shock factor of displaying a
> huge query, which is usually what is involved when using the editor. 

Which is a good indicator that a way to turn it off is a good idea.
Dan Langille : http://www.langille.org/

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?


Reply via email to