view src/testdir/test_python2.vim @ 12505:5cf248ecb6e3 v8.0.1131

patch 8.0.1131: not easy to trigger an autocommand for new terminal window commit https://github.com/vim/vim/commit/b00fdf6eed5fec589a86655249a851c2d9ba3bb8 Author: Bram Moolenaar <Bram@vim.org> Date: Thu Sep 21 22:16:21 2017 +0200 patch 8.0.1131: not easy to trigger an autocommand for new terminal window Problem: It is not easy to trigger an autocommand for new terminal window. (Marco Restelli) Solution: Trigger BufWinEnter after setting 'buftype'.
author Christian Brabandt <cb@256bit.org>
date Thu, 21 Sep 2017 22:30:04 +0200
parents 27b42717662b
children c15bef307de6
line wrap: on
line source

" Test for python 2 commands.
" TODO: move tests from test87.in here.

if !has('python')
  finish
endif

func Test_pydo()
  " Check deleting lines does not trigger ml_get error.
  py import vim
  new
  call setline(1, ['one', 'two', 'three'])
  pydo vim.command("%d_")
  bwipe!

  " Check switching to another buffer does not trigger ml_get error.
  new
  let wincount = winnr('$')
  call setline(1, ['one', 'two', 'three'])
  pydo vim.command("new")
  call assert_equal(wincount + 1, winnr('$'))
  bwipe!
  bwipe!
endfunc