Mercurial > vim
view runtime/tools/vim132 @ 10589:b0c9c1a05054 v8.0.0184
patch 8.0.0184: when an error is caught Vim still exits with non-zero result
commit https://github.com/vim/vim/commit/2b7bc567b9238aaac682236cb4f727d0376e1302
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Jan 14 19:24:52 2017 +0100
patch 8.0.0184: when an error is caught Vim still exits with non-zero result
Problem: When in Ex mode and an error is caught by try-catch, Vim still
exits with a non-zero exit code.
Solution: Don't set ex_exitval when inside a try-catch. (partly by Christian
Brabandt)
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sat, 14 Jan 2017 19:30:03 +0100 |
parents | 3fc0f57ecb91 |
children |
line wrap: on
line source
#!/bin/csh # # Shell script for use with UNIX # Starts up Vim with the terminal in 132 column mode # Only works on VT-100 terminals and lookalikes # You need to have a termcap entry "vt100-w". Same as vt100 but 132 columns. # set oldterm=$term echo "[?3h" setenv TERM vt100-w vim $* set term=$oldterm echo "[?3l"