resent with my real mail address...
On 9 Jan 2003 at 13:45, Peter Mount wrote:
> 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 ;-)
It is easier to edit things within an editor than within the command line,
especially if using very long complex statements involving 8 or 9 tables
and nested/outer JOINS.
--
Dan Langille : http://www.langille.org/
