Mercurial > vim
view runtime/doc/pi_gzip.txt @ 17024:727f8cc87a45 v8.1.1512
patch 8.1.1512: ch_evalexpr() hangs when used recursively
commit https://github.com/vim/vim/commit/38ea784fecf7921dca83ddc75fe9cb40708521b2
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Jun 9 19:51:58 2019 +0200
patch 8.1.1512: ch_evalexpr() hangs when used recursively
Problem: ch_evalexpr() hangs when used recursively. (Paul Jolly)
Solution: Change ch_block_id from a single number to a list of IDs to wait
on.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sun, 09 Jun 2019 20:00:06 +0200 |
parents | 0e473e9e70c2 |
children | af69c9335223 |
line wrap: on
line source
*pi_gzip.txt* For Vim version 8.1. Last change: 2019 May 05 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 ============================================================================== 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:noet:ft=help:norl: