Re: Invisible PROMPT2 - Mailing list pgsql-hackers

From Maxence Ahlouche
Subject Re: Invisible PROMPT2
Date
Msg-id CAJeaomUcgUwpLDReMiViNdFJbfmk2R6XEMp1nqRGX0jLu8tnFw@mail.gmail.com
Whole thread Raw
In response to Re: Invisible PROMPT2  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Invisible PROMPT2  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers


On Wed, 27 Nov 2019 at 17:09, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Good idea, but I think you need to account for "visible" (ie, if the
newline is inside RL_PROMPT_START_IGNORE, it shouldn't change the width).
It might be best to add logic inside the existing "if (visible)" instead
of making a new top-level case.

Right, I assumed that it was safe given that only terminal control characters were invisible.
Since the title of the terminal window can be changed as well via control characters, it's probably better not to make that assumption.

I updated the patch accordingly.
 
Another special case that somebody's likely to whine about is \t, though
to handle that we'd have to make assumptions about the tab stop distance.
Maybe assuming that it's 8 is good enough.

The problem with tabs is that any user can set their tabstops to whatever they want, and a tab doesn't have a fixed width, it just goes up to the next tab stop.
One way to do it would be to add tabs wherever necessary in prompt2 to make sure they have the same size as in prompt1 (a list of numbers of spaces, which we would concatenate with a tab?), but I'm not sure it's worth the effort.

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Avoiding a small risk of failure in timestamp(tz) regression tests
Next
From: Philippe BEAUDOIN
Date:
Subject: Re: Global temporary tables