comparison 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
comparison
equal deleted inserted replaced
23809:0dcd6d533273 23810:8152b7daebad
482 call assert_equal('ansi', &ttytype) 482 call assert_equal('ansi', &ttytype)
483 call assert_equal(&ttytype, &term) 483 call assert_equal(&ttytype, &term)
484 set ttytype=xterm 484 set ttytype=xterm
485 call assert_equal('xterm', &ttytype) 485 call assert_equal('xterm', &ttytype)
486 call assert_equal(&ttytype, &term) 486 call assert_equal(&ttytype, &term)
487 " "set ttytype=" gives E522 instead of E529
488 " in travis on some builds. Why? Catch both for now
489 try 487 try
490 set ttytype= 488 set ttytype=
491 call assert_report('set ttytype= did not fail') 489 call assert_report('set ttytype= did not fail')
492 catch /E529\|E522/ 490 catch /E529/
493 endtry 491 endtry
494 492
495 " Some systems accept any terminal name and return dumb settings, 493 " Some systems accept any terminal name and return dumb settings,
496 " check for failure of finding the entry and for missing 'cm' entry. 494 " check for failure of finding the entry and for missing 'cm' entry.
497 try 495 try