diff src/testdir/test_options.vim @ 23810:8152b7daebad v8.2.2446

patch 8.2.2446: setting 'term' empty has different error if compiled with GUI Commit: https://github.com/vim/vim/commit/5daa91162699e4f8b54f9d1caaaab2715038941c Author: Bram Moolenaar <Bram@vim.org> Date: Mon Feb 1 18:39:47 2021 +0100 patch 8.2.2446: setting 'term' empty has different error if compiled with GUI Problem: Setting 'term' empty has different error if compiled with GUI. Solution: Insert "else". (closes https://github.com/vim/vim/issues/7766)
author Bram Moolenaar <Bram@vim.org>
date Mon, 01 Feb 2021 18:45:06 +0100
parents 2a5b9801f2e2
children bfc1ae959d9d
line wrap: on
line diff
--- a/src/testdir/test_options.vim
+++ b/src/testdir/test_options.vim
@@ -484,12 +484,10 @@ func Test_set_ttytype()
   set ttytype=xterm
   call assert_equal('xterm', &ttytype)
   call assert_equal(&ttytype, &term)
-  " "set ttytype=" gives E522 instead of E529
-  " in travis on some builds. Why?  Catch both for now
   try
     set ttytype=
     call assert_report('set ttytype= did not fail')
-  catch /E529\|E522/
+  catch /E529/
   endtry
 
   " Some systems accept any terminal name and return dumb settings,