view src/testdir/unix.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 bfd636b8e259
children dbec60b8c253
line wrap: on
line source

" Settings for test script execution
" Always use "sh", don't use the value of "$SHELL".
set shell=sh

" Only when the +eval feature is present. 
if 1
  " While some tests overwrite $HOME to prevent them from polluting user files,
  " we need to remember the original value so that we can tell external systems
  " where to ask about their own user settings.
  let g:tester_HOME = $HOME
endif

source setup.vim