Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit7e42478

Browse files
committed
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 thebuildfarm. I'm not happy with anything about the current state,but let's at least try to have a green buildfarm report while furtherinvestigation continues.Discussion:https://postgr.es/m/23181.1578167938@sss.pgh.pa.us
1 parent60ab7c8 commit7e42478

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

‎src/bin/psql/t/010_tab_completion.pl

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -41,9 +41,6 @@
4141
# Debug investigation
4242
note"TERM is set to '" . ($ENV{TERM} ||"<undef>") ."'";
4343

44-
# Ensure that readline/libedit puts out xterm escapes, not something else.
45-
$ENV{TERM} ='xterm';
46-
4744
# regexp to match one xterm escape sequence (CSI style only, for now)
4845
my$escseq ="(\e\\[[0-9;]*[A-Za-z])";
4946

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp