view src/testdir/test_lineending.vim @ 33988:7c30841c60a0 v9.0.2180

patch 9.0.2180: POSIX function name in exarg causes issues Commit: https://github.com/vim/vim/commit/6fdb6280821a822768df5689a5d727e37d38306c Author: Zoltan Arpadffy <zoltan.arpadffy@gmail.com> Date: Tue Dec 19 20:53:07 2023 +0100 patch 9.0.2180: POSIX function name in exarg causes issues Problem: POSIX function name in exarg struct causes issues on OpenVMS Solution: Rename getline member in exarg struct to ea_getline, remove isinf() workaround for VMS There are compilers that do not treat well POSIX functions - like getline - usage in the structs. Older VMS compilers could digest this... but the newer OpenVMS compilers ( like VSI C x86-64 X7.4-843 (GEM 50XB9) ) cannot deal with these structs. This could be limited to getline() that is defined via getdelim() and might not affect all POSIX functions in general - but avoiding POSIX function names usage in the structs is a "safe side" practice without compromising the functionality or the code readability. The previous OpenVMS X86 port used a workaround limiting the compiler capabilities using __CRTL_VER_OVERRIDE=80400000 In order to make the OpenVMS port future proof, this pull request proposes a possible solution. closes: #13704 Signed-off-by: Zoltan Arpadffy <zoltan.arpadffy@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
author Christian Brabandt <cb@256bit.org>
date Tue, 19 Dec 2023 21:00:04 +0100
parents 08940efa6b4e
children
line wrap: on
line source

" Tests for saving/loading a file with some lines ending in
" CTRL-M, some not

func Test_lineending()
  let l = ["this line ends in a\<CR>",
	      \ "this one doesn't",
	      \ "this one does\<CR>",
	      \ "and the last one doesn't"]
  set ta tx
  enew!
  call append(0, l)
  $delete
  write Xfile1
  bwipe Xfile1
  edit Xfile1
  let t = getline(1, '$')
  call assert_equal(l, t)
  new | only
  call delete('Xfile1')
endfunc

" vim: shiftwidth=2 sts=2 expandtab