On Mo, 20 Feb 2017, Marius Bakke wrote: > That patch indeed makes the tests pass in the Guix build environment. > > The test suite is run non-interactively with no controlling `TERM` or > terminfo/termcap files. > > It succeeds when run interactively from an X11 environment.
So here is a proper patch attached. Best, Christian -- Stilblüten aus Schreiben von Versicherungsnehmern: Ich bin von Beruf Schweißer. Ihr Computer hat an der falschen Stelle gespart und bei meinem Beruf das w weggelassen. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
From effe6e8609a0436d3147e1a4a352bc94e4a3ff8f Mon Sep 17 00:00:00 2001 From: Christian Brabandt <[email protected]> Date: Tue, 21 Feb 2017 08:38:19 +0100 Subject: [PATCH] Only try to set the t_k1 option, when it is actually supported When run in a terminal, that has no support for the f1 key, this test fails. It was originally guarded by a !has("gui_running") check, but that is not correct, as it will only skip this test when run in the gui. However if run with TERM=dumb make test_alot.res this will fail, as the termcodes table struct is not set for that key. Fixes #1459 --- src/testdir/test_assign.vim | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/testdir/test_assign.vim b/src/testdir/test_assign.vim index 4a4c644cf..efc9d086b 100644 --- a/src/testdir/test_assign.vim +++ b/src/testdir/test_assign.vim @@ -15,7 +15,7 @@ func Test_let_termcap() call assert_match('t_te.*^[[yes;', execute("set termcap")) let &t_te = old_t_te - if !has('gui_running') + if exists("+t_k1") " Key code let old_t_k1 = &t_k1 let &t_k1 = "that" -- 2.11.0
