view runtime/compiler/fortran_cv.vim @ 13186:dc39ef257b60 v8.0.1467

patch 8.0.1467: libvterm doesn't handle illegal byte sequence correctly commit https://github.com/vim/vim/commit/fef4ddd5eb8816a6607a624aa401bcfa71a63def Author: Bram Moolenaar <Bram@vim.org> Date: Sun Feb 4 14:49:57 2018 +0100 patch 8.0.1467: libvterm doesn't handle illegal byte sequence correctly Problem: Libvterm doesn't handle illegal byte sequence correctly. Solution: After the invalid code check if there is space to store another character. Allocate one more character. (zhykzhykzhyk, closes #2614, closes #2613)
author Christian Brabandt <cb@256bit.org>
date Sun, 04 Feb 2018 15:00:04 +0100
parents 3fc0f57ecb91
children 2704c4e3e20a
line wrap: on
line source

" Vim compiler file
" Compiler:	Compaq Visual Fortran
" Maintainer:	Joh.-G. Simon (johann-guenter.simon@linde-le.com)
" Last Change:	11/05/2002

if exists("current_compiler")
  finish
endif
let current_compiler = "fortran_cv"

if exists(":CompilerSet") != 2		" older Vim always used :setlocal
  command -nargs=* CompilerSet setlocal <args>
endif

let s:cposet = &cpoptions
set cpoptions-=C

" A workable errorformat for Compaq Visual Fortran
CompilerSet errorformat=
		\%E%f(%l)\ :\ Error:%m,
		\%W%f(%l)\ :\ Warning:%m,
		\%-Z%p%^%.%#,
		\%-G%.%#,
" Compiler call
CompilerSet makeprg=df\ /nologo\ /noobj\ /c\ %
" Visual fortran defaults to printing output on stderr
" Adjust option shellpipe accordingly

let &cpoptions = s:cposet
unlet s:cposet