Re: psql and readline

From: Rod Taylor <rbt(at)rbt(dot)ca>
To: Justin Clift <justin(at)postgresql(dot)org>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Dan Langille <dan(at)langille(dot)org>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql and readline
Date: 2003-01-09 15:25:30
Message-ID: 1042125929.52087.7.camel@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2003-01-09 at 10:12, 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".

We could always create a new command that edits a query buffer rather
than file

\e FILENAME

\E QUERY BUFFER

So, history of:
\E SELECT .......

Selecting this would fire off an editor based on the query to the right
of the command, much as \e FILENAME opens an editor based on the file to
the right of the command.
--
Rod Taylor <rbt(at)rbt(dot)ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message cbbrowne 2003-01-09 15:34:59 Re: psql and readline
Previous Message Lee Kindness 2003-01-09 15:25:07 Re: [PATCHES] PostgreSQL libraries - PThread Support, but not use...