Mercurial > vim
view runtime/doc/ft_ps1.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 | 43593a5d873f |
| children |
line wrap: on
line source
*ft_ps1.txt* A Windows PowerShell syntax plugin for Vim Author: Peter Provost <https://www.github.com/PProvost> License: Apache 2.0 URL: https://github.com/PProvost/vim-ps1 INTRODUCTION *ps1-syntax* This plugin provides Vim syntax, indent and filetype detection for Windows PowerShell scripts, modules, and XML configuration files. ABOUT *ps1-about* Grab the latest version or report a bug on GitHub: https://github.com/PProvost/vim-ps1 FOLDING *ps1-folding* The ps1 syntax file provides syntax folding (see |:syn-fold|) for script blocks and digital signatures in scripts. When 'foldmethod' is set to "syntax" then function script blocks will be folded unless you use the following in your .vimrc or before opening a script: > :let g:ps1_nofold_blocks = 1 < Digital signatures in scripts will also be folded unless you use: > :let g:ps1_nofold_sig = 1 < Note: syntax folding might slow down syntax highlighting significantly, especially for large files. COMPILER *ps1-compiler* The powershell `:compiler` script configures |:make| to execute the script in PowerShell. It tries to pick a smart default PowerShell command: `pwsh` if available and `powershell` otherwise, but you can customize the command: > :let g:ps1_makeprg_cmd = '/path/to/pwsh' < To configure whether to show the exception type information: > :let g:ps1_efm_show_error_categories = 1 < KEYWORD LOOKUP *ps1-keyword* To look up keywords using PowerShell's Get-Help, press the |K| key. For more convenient paging, the pager `less` should be installed, which is included in many Linux distributions and in macOS. Many other distributions are available for Windows like https://chocolatey.org/packages/less/. Make sure `less` is in a directory listed in the `PATH` environment variable, which chocolatey above does. ------------------------------------------------------------------------------ vim:ft=help: