Mercurial > vim
view runtime/tools/ccfilter_README.txt @ 34379:37b4c89ba420 v9.1.0116
patch 9.1.0116: win_split_ins may not check available room
Commit: https://github.com/vim/vim/commit/0fd44a5ad81ade342cb54d8984965bdedd2272c8
Author: Sean Dewar <6256228+seandewar@users.noreply.github.com>
Date: Tue Feb 20 20:28:15 2024 +0100
patch 9.1.0116: win_split_ins may not check available room
Problem: win_split_ins has no check for E36 when moving an existing
window
Solution: check for room and fix the issues in f_win_splitmove()
(Sean Dewar)
win_split_ins has no check for E36 when moving an existing window,
allowing for layouts with many overlapping zero-sized windows to be
created (which may also cause drawing issues with tablines and such).
f_win_splitmove also has some bugs.
So check for room and fix the issues in f_win_splitmove. Handle failure
in the two relevant win_split_ins callers by restoring the original
layout, and factor the common logic into win_splitmove.
Don't check for room when opening an autocommand window, as it's a
temporary window that's rarely interacted with or drawn anyhow, and is
rather important for some autocommands.
Issues fixed in f_win_splitmove:
- Error if splitting is disallowed.
- Fix heap-use-after-frees if autocommands fired from switching to "targetwin"
close "wp" or "oldwin".
- Fix splitting the wrong window if autocommands fired from switching to
"targetwin" switch to a different window.
- Ensure -1 is returned for all errors.
Also handle allocation failure a bit earlier in make_snapshot (callers,
except win_splitmove, don't really care if a snapshot can't be made, so
just ignore the return value).
Note: Test_smoothscroll_in_zero_width_window failed after these changes with
E36, as it was using the previous behaviour to create a zero-width window.
I've fixed the test such that it fails with UBSAN as expected when v9.0.1367 is
reverted (and simplified it too).
related: #14042
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 | Tue, 20 Feb 2024 22:30:04 +0100 |
parents | e751b5c9dff3 |
children |
line wrap: on
line source
READ THIS FIRST =============== ccfilter is a C program to filter the output of a few compilers to a common QuickFix format. It is provided with Vim to make quickfix useful for more compilers. ccfilter WILL FAIL with long lines (more than 2047 bytes). COMPILING AND INSTALLING: ========================= To compile ccfilter, you can just do a plain: cc ccfilter.c -o ccfilter Though, it may be wise to have your default compiler defined, so you would normally compile it with one of the following: cc -D_GCC ccfilter.c -o ccfilter cc -D_AIX ccfilter.c -o ccfilter cc -D_ATT ccfilter.c -o ccfilter cc -D_IRIX ccfilter.c -o ccfilter cc -D_SOLARIS ccfilter.c -o ccfilter cc -D_HPUX ccfilter.c -o ccfilter You can then copy ccfilter to its target destination (i.e: /usr/local/bin). The man page ccfilter.1 has to be copied to somewhere in your MANPATH, under a man1 directory (i.e: /usr/local/man/man1). SUPPORTED COMPILERS/PORTING NOTES: ================================== The supported formats for the different compilers are described below: In this section, meta-names are used as place-holders in the line formats: <FILE> <ROW> <COL> <SEVERITY> <REASON> <> The <> denotes ignored text. Line formats are delimited by the ^ (caret) symbol. 0) Special case: "gmake directory change" lines: Lines with a format like: ^gmake[<NUM>]: Entering directory `<DIR>'^ are used to follow the directory changes during the make process, providing in the <FILE> part, a relative (if possible) directory path to the erroneous file. 1) GCC: Recognized lines are of the format: - ^In file included from <FILE>:<ROW>:^ Line following this one is used as <REASON> <SEVERITY> is always 'e' (error) <COL> is always '0' - ^<FILE>:<ROW>:<REASON>^ <SEVERITY> is always 'e' (error) <COL> is always '0' 2) AIX: Recognized lines are of the format: - ^"<FILE>", line <ROW>.<COL>: <> (<SEVERITY>) <REASON>", 3) HPUX: Recognized lines are of the format: - ^cc: "<FILE>", line <ROW>: <SEVERITY>: <REASON>^ <COL> is always '0' 4) SOLARIS: Recognized lines are of the format: - ^"<FILE>", line <ROW>: warning: <REASON>^ This assumes <SEVERITY> is "W" <COL> is always '0' - ^"<FILE>", line <ROW>: <REASON>^ This assumes <SEVERITY> is "E" <COL> is always '0' 5) ATT / NCR: Recognized lines are of the format: - ^<SEVERITY> "<FILE>",L<ROW>/C<COL><>:<REASON>^ or - ^<SEVERITY> "<FILE>",L<ROW>/C<COL>:<REASON>^ Following lines beginning with a pipe (|) are continuation lines, and are therefore appended to the <REASON> - ^<SEVERITY> "<FILE>",L<ROW>:<REASON>^ <COL> is '0' Following lines beginning with a pipe (|) are continuation lines, and are therefore appended to the <REASON> 6) SGI-IRIX: Recognized lines are of the format: - ^cfe: <SEVERITY>: <FILE>: <ROW>: <REASON>^ or ^cfe: <SEVERITY>: <FILE>, line <ROW>: <REASON>^ Following lines beginning with a dash (-) are "column-bar" that end with a caret in the column of the error. These lines are analyzed to generate the <COL>.