From 7e42478186aa8b41a8706f3f53b44e25a427bde9 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 4 Jan 2020 16:40:56 -0500 Subject: [PATCH] Don't try to force TERM to a fixed value in tab-completion test. 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 --- src/bin/psql/t/010_tab_completion.pl | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/bin/psql/t/010_tab_completion.pl b/src/bin/psql/t/010_tab_completion.pl index 1dc87b504fa..0f1d596b2bf 100644 --- a/src/bin/psql/t/010_tab_completion.pl +++ b/src/bin/psql/t/010_tab_completion.pl @@ -41,9 +41,6 @@ $ENV{PSQL_HISTORY} = $historyfile; # Debug investigation note "TERM is set to '" . ($ENV{TERM} || "") . "'"; -# 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])";