Mercurial > vim
view runtime/tools/ccfilter.1 @ 34538:c865c2f93a04 v9.1.0171
patch 9.1.0171: Small split-move related improvements
Commit: https://github.com/vim/vim/commit/5cac1a9bee0798d70a7fd80363a1f697759638e8
Author: Sean Dewar <6256228+seandewar@users.noreply.github.com>
Date: Tue Mar 12 21:11:39 2024 +0100
patch 9.1.0171: Small split-move related improvements
Problem: small improvements can be made to split-move related
functions.
Solution: apply them (Sean Dewar):
- Improve some doc comments (frame_flatten should still work for non-current
tabpages, despite the topframe check, which looks benign, though I'm unsure if
it's still needed; see #2467).
- f_win_splitmove should check_split_disallowed on wp, not targetwin, as that's
what win_splitmove checks (though it's probably unnecessary to check
b_locked_split at all; see #14109, which I hope to get around to finishing at
some point).
- Make winframe_restore restore window positions for the altframe, which
winframe_remove changes. This doesn't affect the prior behaviour, as we called
win_comp_pos after, but as win_comp_pos only works for curtab, and
winframe_remove supports non-current tabpages, we should undo it. Regardless,
this should mean we don't need win_comp_pos anymore; adjust tests to check
that window positions remain unchanged.
I'm not sure win_comp_pos is needed after last_status anyway if it doesn't
steal rows from another frame to make room for a new statusline, which
shouldn't be the case after winframe_remove? To be safe, I'll leave it as is.
closes: #14185
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, 12 Mar 2024 21:15:03 +0100 |
| parents | 2b30a2b4bde2 |
| children |
line wrap: on
line source
.TH ccfilter 1 "01-Apr-97" .SH NAME ccfilter \- a compiler's output filter for vim quickfix .SH SYNOPSIS ccfilter [ .B <options> ] .SH DESCRIPTION The ccfilter utility "filters" the output of several compilers and makers (make/gmake) from several platforms (see NOTES below) to a standardized format which easily fits in vim's quickfix feature. For further details, see in vim ":help quickfix". .PP ccfilter reads .B 'stdin' and outputs to .B 'stdout' \. .PP The need for ccfilter is clear, as some compilers have irregular and/or multiple line error messages (with the relevant information on line 2), which makes it impossible for the errorformat to correctly display them ! When working on different platforms, and with different compilers, ccfilter eases the utilization of quickfix, due to its standardized output, allowing to have in .vimrc a plain .br .B \ \ \ \ :set\ errorformat=%f:%l:%c:%t:%m .SH USAGE When using ccfilter, one would include the following lines in .vimrc: .br .B \ \ \ \ :set shellpipe=\\\\|&ccfilter\\\\> .br .B \ \ \ \ :set errorformat=%f:%l:%c:%t:%m .SH OPTIONS .TP 16 -c Decrement column by one. This may be needed, depending on the compiler being used. .TP -r Decrement row by one. This may be needed, depending on the compiler being used. .TP -v Verbose (Outputs also invalid lines). This option makes ccfilter output also the lines that couldn't be correctly parsed. This is used mostly for ccfilter debugging. .TP -o <COMPILER> Treat input as <COMPILER>'s output. Even when configuring ccfilter to assume a default COMPILER, sometimes it's helpful to be able to specify the COMPILER used to generate ccfilter's input. For example, when cross-compiling on a network from a single machine. .TP -h Shows a brief help, describing the configured default COMPILER and the valid parameters for COMPILER. .SH NOTES Currently, ccfilter accepts output from several compilers, as described below: .TP 10 GCC GCC compiler .TP AIX AIX's C compiler .TP ATT AT&T/NCR's High Performance C Compiler .TP IRIX IRIX's MIPS/MIPSpro C compiler .TP SOLARIS SOLARIS's SparcWorks C compiler .TP HPUX HPUX's C compiler .SH AUTHOR .B ccfilter was developed by .B Pablo Ariel Kohan .BR .B mailto:pablo@memco.co.il