Re: Confusing behavior of psql's \e - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: Confusing behavior of psql's \e
Date
Msg-id 10a183c69ede6d8ce0f82eb60f891ec0d1dfc5ec.camel@cybertec.at
Whole thread Raw
In response to Re: Confusing behavior of psql's \e  (Chapman Flack <chap@anastigmatix.net>)
Responses Re: Confusing behavior of psql's \e
List pgsql-hackers
On Tue, 2020-12-01 at 11:03 -0500, Chapman Flack wrote:
> On 11/30/20 22:38, Laurenz Albe wrote:
> > I have been annoyed about this myself, and I have heard other prople
> > complain about it, so I propose to clear the query buffer if the
> > editor exits without modifying the file.
> 
> Or how about keeping the query buffer content unchanged, but not
> executing it? Then it's still there if you have another idea about
> editing it. It's easy enough to \r if you really want it gone.

What if the buffer was empty?  Would you want to get the previous
query in the query buffer?  I'd assume not...

Yours,
Laurenz Albe




pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Avoid using lcons and list_delete_first in plan_union_children()
Next
From: Magnus Hagander
Date:
Subject: Re: Add session statistics to pg_stat_database