Greetings:
Some man page headers and footers are not highlighted properly. Examples
on Debian 10 include "man last" and "man ufw".
This commit changes the highlighting rules to always highlight the first
and last lines, regardless of their form. This means that man pages
that look like (in the
Patch 8.2.0582
Problem:Color ramp test does not show text colors.
Solution: Add a row of 16 text colors and 16 bold text colors.
Files: src/testdir/color_ramp.vim
*** ../vim-8.2.0581/src/testdir/color_ramp.vim 2017-11-26 17:14:38.0
+0100
--- src/testdir/color_ramp.vim
Don't you need to disown?
> Am 15.04.2020 um 21:15 schrieb lifecrisis (Vim Github Repository)
> :
>
>
> Hmmm... I don't think that's correct. :/
>
> The shell terminates, but leaves behind a background process (a "zombie", I
> think).
>
> You can see this with bash fairly easily. Please
Patch 8.2.0581 (after 8.2.0547)
Problem:Win32 console: the cursor position is always top-left.
Solution: Revert the patch for restoring screen.
Files: src/os_win32.c
*** ../vim-8.2.0580/src/os_win32.c 2020-04-12 19:37:13.522297249 +0200
--- src/os_win32.c 2020-04-15
Tony wrote:
> After sending a message to the address vim-p...@googlegroups.com
> mentioned as "maintainer" at top of the Perl ftplugin
> $VIMRUNTIME/ftplugin/perl.vim I got the message below. IIUC this means
> that the maintainer address should be changed. The syntax and indent
> perl.vim
Yegappan wrote:
> Currently when using a heredoc with the :let statement, you have to
> specify an explicit marker both at the beginning and at the end of the
> statement. But when using the heredoc with embedded
> scripts (e.g. python), you don't need to specify an explicit marker at the
>
Mark Waggoner wrote:
> Here's a test:
Thanks! Always nice when someone fixes the problem they reported
themselves :-).
--
"The future's already arrived - it's just not evenly distributed yet."
-- William Gibson
/// Bram Moolenaar -- b...@moolenaar.net --
Christian Brabandt wrote:
> On Mi, 15 Apr 2020, Dominique Pellé wrote:
>
> > Patrick Byrne wrote:
> >
> > > The vim docs say sgr should be set if xterm is v277 or later.
> > > The xterm binary on my system is 295 which is later, but
> > > I worry it is getting the version information from
Patch 8.2.0580
Problem:Window size wrong if 'ea' is off and 'splitright' is on and
splitting then closing a window.
Solution: Put abandoned window space in the right place. (Mark Waggoner)
Files: src/testdir/test_winbuf_close.vim, src/window.c
***
On Mi, 15 Apr 2020, Christian Brabandt wrote:
> diff --git a/src/term.c b/src/term.c
> index ce935dcf4..fc0febba1 100644
> --- a/src/term.c
> +++ b/src/term.c
> @@ -4783,7 +4783,11 @@ not_enough:
> // PuTTY sends 0;136;0
> // vandyke SecureCRT
Gary Johnson wrote:
> On 2019-05-20, Bram Moolenaar wrote:
> > > > Solution: Only use the "extends" character when 'list' is on.
> > > (Hirohito
> > > > Higashi, closes #4360)
> > >
> > > This change may be consistent, but is it helpful?
> >
> > It was a bit of a mistake to
On Mi, 15 Apr 2020, Dominique Pellé wrote:
> Patrick Byrne wrote:
>
> > The vim docs say sgr should be set if xterm is v277 or later.
> > The xterm binary on my system is 295 which is later, but
> > I worry it is getting the version information from putty somehow.
>
> It looks like vim's
Patrick Byrne wrote:
> The vim docs say sgr should be set if xterm is v277 or later.
> The xterm binary on my system is 295 which is later, but
> I worry it is getting the version information from putty somehow.
It looks like vim's default value of 'ttymouse' is suboptimal
when using the PuTTY
The vim docs say sgr should be set if xterm is v277 or later. The xterm
binary on my system is 295 which is later, but I worry it is getting the
version information from putty somehow. I can't see any xterm version
information in the putty configuration dialog.
':verbose set ttymouse?' just
Patrick Byrne wrote:
> Yes 'sgr' did it - thanks! Sorry I assumed it was a bug.
> Perhaps 'sgr' ought to be the default these days.
> Cheers
> Patrick
Not sure how many terminals support sgr which supports more columns/rows.
Probably most of them support sgr these days.
In fact ":help ttymouse"
Yes 'sgr' did it - thanks! Sorry I assumed it was a bug. Perhaps 'sgr'
ought to be the default these days.
Cheers
Patrick
On Wednesday, 15 April 2020 11:57:29 UTC+1, Christian Brabandt wrote:
>
>
> On Mi, 15 Apr 2020, Patrick Byrne wrote:
>
> > It is xterm2. I tried changing it to xterm and
On Mi, 15 Apr 2020, Patrick Byrne wrote:
> It is xterm2. I tried changing it to xterm and same problem (plus I don't see
> selection update interactively - which I suppose it expected behaviour).
I think you need sgr
Best,
Christian
--
Stilblüten aus Schreiben von Versicherungsnehmern:
Ich
It is xterm2. I tried changing it to xterm and same problem (plus I don't
see selection update interactively - which I suppose it expected behaviour).
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more
On Mi, 15 Apr 2020, Patrick Byrne wrote:
> Hi,
>
> I have a problem selecting text with the mouse in vim.
>
> My monitor is 34" widescreen 2560x1080. Thats 284 columns in vim. I can only
> select up to column 223 using the mouse. I can still select and edit using
> keys
> in the columns
Hi,
I have a problem selecting text with the mouse in vim.
My monitor is 34" widescreen 2560x1080. Thats 284 columns in vim. I can
only select up to column 223 using the mouse. I can still select and edit
using keys in the columns right of here.
2560 / 283 is 9 pixels per character width, so
20 matches
Mail list logo
