psql: tab completion differs on semicolon placement - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject psql: tab completion differs on semicolon placement
Date
Msg-id 44786457-3E92-4162-9AFC-1E0328792BF6@yesql.se
Whole thread Raw
Responses Re: psql: tab completion differs on semicolon placement  (Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>)
List pgsql-hackers
While testing a patch I fat-fingered a CREATE DATABASE statement by tab
completing *after* the semicolon, with no space between the objname and
semicolon.  The below options were presented, which at this point aren't really
applicable:

db=# create database foo;
ALLOW_CONNECTIONS ENCODING          LC_COLLATE        LOCALE            TABLESPACE
CONNECTION LIMIT  IS_TEMPLATE       LC_CTYPE          OWNER             TEMPLATE

DROP DATABASE has a similar tab completion which makes about as much sense:

db=# drop database foo;WITH (

Checking prev_wd for not ending with ';' as per the attached makes "objname;"
behave like "objname ;".  Is there a reason for not doing that which I'm
missing?  I didn't check for others, but if this seems reasonable I'll go
through to find any other similar cases.

--
Daniel Gustafsson        https://vmware.com/


Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Logical replication timeout problem
Next
From: Dilip Kumar
Date:
Subject: Re: row filtering for logical replication