Re: psql and readline - Mailing list pgsql-hackers

From Peter Mount
Subject Re: psql and readline
Date
Msg-id Pine.LNX.4.44.0301091344390.1613-100000@localhost.localdomain
Whole thread Raw
In response to Re: psql and readline  ("Dan Langille" <dan@langille.org>)
Responses Re: psql and readline
Re: psql and readline
List pgsql-hackers
On Wed, 8 Jan 2003, Dan Langille wrote:

> On 8 Jan 2003 at 12:28, Bruce Momjian wrote:
> 
> > Tom Lane wrote:
> > > "Alexander M. Pravking" <fduch@antar.bryansk.ru> writes:
> > > > On Wed, Jan 08, 2003 at 10:53:51AM +0100, Ian Barwick wrote:
> > > >> On Wednesday 08 January 2003 07:55, Christopher Kings-Lynne
> > > >> wrote:
> > > >>> Is there any way of making the 'up' arrow retrieve all of the
> > > >>> last multiline query, instead of just the last line?  It's
> > > >>> really annoying working with large multiline queries at the
> > > >>> moment...
> > > >> 
> > > >> Not that I know of, but you can use \e to edit the query in your
> > > >> favourite editor.
> > > 
> > > > Sure. But \e puts "\e" into history, instead of the query itself
> > > > :(
> > > 
> > > Hm, so it does.  It seems like the edited query should go into
> > > history, at least when you execute it.  Peter, is this fixable?
> > 
> > Wow, that would be a nifty trick, though they really did type \e and
> > not the query the pulled in from the editor.
> 
> What about those of us who want to use \e repeatedly?  Will that be 
> in the history buffer?

The number of times I've cursed things over the years, I would have 
thought having the edited query in the history would be more useful than 
\e - the latter is only three key presses any how ;-)

Peter

-- 
Peter Mount
peter@retep.org.uk
http://www.retep.org.uk/Tel/Fax: +44 (0) 1622 749439 Mobile: +44 (0) 7903 155887 US Fax: 1 435 304 5165
US Voice: 1 435 304 5165




pgsql-hackers by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: MOVE LAST: why?
Next
From: Lee Kindness
Date:
Subject: Re: PostgreSQL libraries - PThread Support, but not use...