Mercurial > vim
view runtime/doc/pi_gzip.txt @ 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 | 368468ef35cf |
children | 1174611ad715 |
line wrap: on
line source
*pi_gzip.txt* For Vim version 8.0. Last change: 2016 Nov 06 VIM REFERENCE MANUAL by Bram Moolenaar Editing compressed files with Vim *gzip* *bzip2* *compress* 1. Autocommands |gzip-autocmd| The functionality mentioned here is a |standard-plugin|. This plugin is only available if 'compatible' is not set. You can avoid loading this plugin by setting the "loaded_gzip" variable: > :let loaded_gzip = 1 {Vi does not have any of this} ============================================================================== 1. Autocommands *gzip-autocmd* The plugin installs autocommands to intercept reading and writing of files with these extensions: extension compression ~ *.Z compress (Lempel-Ziv) *.gz gzip *.bz2 bzip2 *.lzma lzma *.xz xz *.lz lzip *.zst zstd That's actually the only thing you need to know. There are no options. After decompressing a file, the filetype will be detected again. This will make a file like "foo.c.gz" get the "c" filetype. If you have 'patchmode' set, it will be appended after the extension for compression. Thus editing the patchmode file will not give you the automatic decompression. You have to rename the file if you want this. ============================================================================== vim:tw=78:ts=8:ft=help:norl: