Mercurial > vim
annotate runtime/doc/pi_gzip.txt @ 34548:db67c09ccd53 v9.1.0175
patch 9.1.0175: wrong window positions with 'winfix{width,height}'
Commit: https://github.com/vim/vim/commit/5866bc3a0f54115d5982fdc09bdbe4c45069265a
Author: Sean Dewar <6256228+seandewar@users.noreply.github.com>
Date: Wed Mar 13 20:17:24 2024 +0100
patch 9.1.0175: wrong window positions with 'winfix{width,height}'
Problem: winframe functions incorrectly recompute window positions if
the altframe wasn't adjacent to the closed frame, which is
possible if adjacent windows had 'winfix{width,height}' set.
Solution: recompute for windows within the parent of the altframe and
closed frame. Skip this (as before) if the altframe was
top/left, but only if adjacent to the closed frame, as
positions won't change in that case. Also correct the return
value documentation for win_screenpos. (Sean Dewar)
The issue revealed itself after removing the win_comp_pos call below
winframe_restore in win_splitmove. Similarly, wrong positions could result from
windows closed in other tabpages, as win_free_mem uses winframe_remove (at least
until it is entered later, where enter_tabpage calls win_comp_pos).
NOTE: As win_comp_pos handles only curtab, it's possible via other means for
positions in non-current tabpages to be wrong (e.g: after changing 'laststatus',
'showtabline', etc.). Given enter_tabpage recomputes it, maybe it's intentional
as an optimization? Should probably be documented in win_screenpos then, but I
won't address that here.
closes: #14191
Signed-off-by: Sean Dewar <6256228+seandewar@users.noreply.github.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Wed, 13 Mar 2024 20:30:03 +0100 |
parents | 4635e43f2c6f |
children |
rev | line source |
---|---|
34057
4635e43f2c6f
patch 9.1.0000: Vim 9.1 release
Christian Brabandt <cb@256bit.org>
parents:
33766
diff
changeset
|
1 *pi_gzip.txt* For Vim version 9.1. Last change: 2023 Nov 14 |
7 | 2 |
3 | |
4 VIM REFERENCE MANUAL by Bram Moolenaar | |
5 | |
6 | |
7 Editing compressed files with Vim *gzip* *bzip2* *compress* | |
8 | |
9 1. Autocommands |gzip-autocmd| | |
10 | |
11 The functionality mentioned here is a |standard-plugin|. | |
12 This plugin is only available if 'compatible' is not set. | |
13 You can avoid loading this plugin by setting the "loaded_gzip" variable: > | |
14 :let loaded_gzip = 1 | |
33721
d7ac49e53d62
runtime(doc): document vim-script library function
Christian Brabandt <cb@256bit.org>
parents:
29314
diff
changeset
|
15 < |
d7ac49e53d62
runtime(doc): document vim-script library function
Christian Brabandt <cb@256bit.org>
parents:
29314
diff
changeset
|
16 *g:gzip_exec* |
d7ac49e53d62
runtime(doc): document vim-script library function
Christian Brabandt <cb@256bit.org>
parents:
29314
diff
changeset
|
17 |
d7ac49e53d62
runtime(doc): document vim-script library function
Christian Brabandt <cb@256bit.org>
parents:
29314
diff
changeset
|
18 For security reasons, one may prevent that Vim runs executables automatically |
d7ac49e53d62
runtime(doc): document vim-script library function
Christian Brabandt <cb@256bit.org>
parents:
29314
diff
changeset
|
19 when opening a buffer. This option (default: "1") can be used to prevent |
d7ac49e53d62
runtime(doc): document vim-script library function
Christian Brabandt <cb@256bit.org>
parents:
29314
diff
changeset
|
20 executing the executables command when set to "0": > |
d7ac49e53d62
runtime(doc): document vim-script library function
Christian Brabandt <cb@256bit.org>
parents:
29314
diff
changeset
|
21 :let g:gzip_exec = 0 |
d7ac49e53d62
runtime(doc): document vim-script library function
Christian Brabandt <cb@256bit.org>
parents:
29314
diff
changeset
|
22 < |
7 | 23 |
24 ============================================================================== | |
33766
fc557aa379ef
runtime(doc): fix typo in pi_gzip.txt
Christian Brabandt <cb@256bit.org>
parents:
33721
diff
changeset
|
25 1. Autocommands *gzip-autocmd* |
7 | 26 |
27 The plugin installs autocommands to intercept reading and writing of files | |
28 with these extensions: | |
29 | |
30 extension compression ~ | |
31 *.Z compress (Lempel-Ziv) | |
32 *.gz gzip | |
33 *.bz2 bzip2 | |
3713 | 34 *.lzma lzma |
35 *.xz xz | |
10319
169a62d5bcb9
commit https://github.com/vim/vim/commit/b4ada79aa7d0d1e5da3a659b1a203d7cae9f7f59
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
36 *.lz lzip |
10385
368468ef35cf
commit https://github.com/vim/vim/commit/c0514bf4777a1d55f5785b3887c5686fd0bbe870
Christian Brabandt <cb@256bit.org>
parents:
10319
diff
changeset
|
37 *.zst zstd |
7 | 38 |
39 That's actually the only thing you need to know. There are no options. | |
40 | |
41 After decompressing a file, the filetype will be detected again. This will | |
42 make a file like "foo.c.gz" get the "c" filetype. | |
43 | |
44 If you have 'patchmode' set, it will be appended after the extension for | |
45 compression. Thus editing the patchmode file will not give you the automatic | |
46 decompression. You have to rename the file if you want this. | |
47 | |
48 ============================================================================== | |
14421 | 49 vim:tw=78:ts=8:noet:ft=help:norl: |