view src/testdir/test_plus_arg_edit.vim @ 17470:d2a834aa7cc0 v8.1.1733

patch 8.1.1733: the man ftplugin leaves an empty buffer behind commit https://github.com/vim/vim/commit/e5e6950193ddf365c6c507ddefcd7f9db939e5ac Author: Bram Moolenaar <Bram@vim.org> Date: Mon Jul 22 22:09:21 2019 +0200 patch 8.1.1733: the man ftplugin leaves an empty buffer behind Problem: The man ftplugin leaves an empty buffer behind. Solution: Don't make new window and edit, use split. (Jason Franklin)
author Bram Moolenaar <Bram@vim.org>
date Mon, 22 Jul 2019 22:15:04 +0200
parents 2dcaa860e3fc
children 2f4be7ca1b1b
line wrap: on
line source

" Tests for complicated + argument to :edit command
function Test_edit()
  call writefile(["foo|bar"], "Xfile1")
  call writefile(["foo/bar"], "Xfile2")
  edit +1|s/|/PIPE/|w Xfile1| e Xfile2|1 | s/\//SLASH/|w
  call assert_equal(["fooPIPEbar"], readfile("Xfile1"))
  call assert_equal(["fooSLASHbar"], readfile("Xfile2"))
  call delete('Xfile1')
  call delete('Xfile2')
endfunction

func Test_edit_bad()
  " Test loading a utf8 file with bad utf8 sequences.
  call writefile(["[\xff][\xc0][\xe2\x89\xf0][\xc2\xc2]"], "Xfile")
  new

  " Without ++bad=..., the default behavior is like ++bad=?
  e! ++enc=utf8 Xfile
  call assert_equal('[?][?][???][??]', getline(1))

  e! ++enc=utf8 ++bad=_ Xfile
  call assert_equal('[_][_][___][__]', getline(1))

  e! ++enc=utf8 ++bad=drop Xfile
  call assert_equal('[][][][]', getline(1))

  e! ++enc=utf8 ++bad=keep Xfile
  call assert_equal("[\xff][\xc0][\xe2\x89\xf0][\xc2\xc2]", getline(1))

  call assert_fails('e! ++enc=utf8 ++bad=foo Xfile', 'E474:')

  bw!
  call delete('Xfile')
endfunc