mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Don't try to force TERM to a fixed value in tab-completion test.

Browse Source 
Right at the moment, this is making things worse not better in the
buildfarm.  I'm not happy with anything about the current state,
but let's at least try to have a green buildfarm report while further
investigation continues.

Discussion: https://postgr.es/m/23181.1578167938@sss.pgh.pa.us
This commit is contained in:
Tom Lane 2020-01-04 16:40:56 -05:00
parent 60ab7c80b4
commit 7e42478186
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/bin/psql/t/010_tab_completion.pl
View File

@ -41,9 +41,6 @@ $ENV{PSQL_HISTORY} = $historyfile;
# Debug investigation
note "TERM is set to '" . ($ENV{TERM} || "<undef>") . "'";
# Ensure that readline/libedit puts out xterm escapes, not something else.
$ENV{TERM} = 'xterm';
# regexp to match one xterm escape sequence (CSI style only, for now)
my $escseq = "(\e\\[[0-9;]*[A-Za-z])";