Re: BUG #15002: Unexpected behaviour in psql \r command

In this case \r subcommand seems to be completely useless.
It does absolutely nothing.

2018-01-09 20:58 GMT+03:00 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>:

> On Tue, Jan 9, 2018 at 10:45 AM, PG Bug reporting form <
> noreply(at)postgresql(dot)org> wrote:
>
>> Previously (at least in 9.6) previous_buf hasn’t been used for any kinds
>> of
>> \e subcommand.
>> Now if query_buf is empty previous buffer contents is used.
>>
>
> ​IIUC the complaint is that it is no longer possible to use \edit​ to
> generate a completely empty temporary query that can then be written from
> scratch.
>
> The v10 behavior is desirable so that leaves either learning a new idiom
> to accomplish your goal or adding something like "\edit -" to explicitly
> invoke the desired behavior.
>
> Doing:
>
> # SELECT <enter>
> # \edit
>
> Seems reasonably straight forward to get a editor for a newly query
> instead of the previous one.
>
> David J.
>
>