Re: [PATCH] Add support to psql for edit-and-execute-command

From: "Joe Wildish" <joe(at)lateraljoin(dot)com>
To: "Oleksandr Shulgin" <oleksandr(dot)shulgin(at)zalando(dot)de>
Cc: "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Add support to psql for edit-and-execute-command
Date: 2020-05-18 10:04:56
Message-ID: F322D695-73A0-4318-90FE-CBC2DE5BA907@lateraljoin.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 18 May 2020, at 7:08, Oleksandr Shulgin wrote:

> The only difference from \e is that you don't need to jump to the end
> of
> input first, I guess?

AIUI, \e will edit the last thing in history or a specific line number
from history, whereas the patch will allow the current line to be
edited. That is 99% of the time what I want.

My work flow is typically "Run some queries" => "Go back to some recent
query by searching history, often not the most recent" => "Edit query".
To do the edit in an editor (without the patch), I've been deliberately
nobbling the query once found from history. This allows it to execute
(and fail) but places it as the most recent thing in history. Then I hit
"\e".

-Joe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2020-05-18 10:09:16 Re: [PATCH] Add support to psql for edit-and-execute-command
Previous Message Etsuro Fujita 2020-05-18 10:00:30 Re: Optimizer docs typos