Re: Correct handling of blank/commented lines in PSQL interactive-mode history

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Greg Nancarrow <gregn4422(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Correct handling of blank/commented lines in PSQL interactive-mode history
Date: 2021-09-07 19:16:25
Message-ID: 3210474.1631042185@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

[ this is a digression from the main point of the thread, but ... ]

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> I am particularly bothered by the uselessness
> that M-# results in -- namely, inserting a # at the start of the buffer.

Fixing that might be as simple as the attached. I've not beat on
it hard though.

regards, tom lane

Attachment Content-Type Size
fix-readline-comment-begin-0.1.patch text/x-diff 583 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-09-07 19:27:27 Re: Don't clean up LLVM state when exiting in a bad way
Previous Message Gavin Flower 2021-09-07 19:15:08 Re: Data loss when '"json_populate_recorset" with long column name