Re: psql and readline - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: psql and readline
Date
Msg-id 200301091513.h09FDEw14061@candle.pha.pa.us
Whole thread Raw
In response to Re: psql and readline  (Justin Clift <justin@postgresql.org>)
Responses Re: psql and readline
Re: psql and readline
List pgsql-hackers
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.  I
don't feel strongly either way --- I am just pointing out the issue.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Justin Clift
Date:
Subject: Re: psql and readline
Next
From: Peter Mount
Date:
Subject: Re: psql and readline