Yegappan wrote:
> When converting test29 into a new style test, I came across several
> instances where multiple lines of text need to be stored in a variable.
> I used the following method to do it:
>
> new
> insert
> some text
> some text
> some text
> .
>
> let text = getline(1, '$')
Patch 8.1.1332
Problem:Cannot flush change listeners without also redrawing. The line
numbers in the list of changes may become invalid.
Solution: Add listener_flush(). Invoke listeners before adding a change
that makes line numbers invalid.
Files: src/evalfun
> I'll make a patch that does this, please check it out.
Thanks, Bram. I'll only properly get a chance to look this weekend.
As you said this function is quite low level. Thinking about govim,
what I'm going to want is the lowest cost means of translating a
callback to the listener into an LSP de
I wrote:
> > Paul Jolly wrote:
> >
> > > > Yesterday I sent out patch 8.1.1321 which adds listener_add().
> > > > This makes it possible to find out about text changes and possibly
> > > > update text properties or anything else.
> > >
> > > Hi Bram - this is fantastic, thanks. I look forward
> I cannot reproduce this in xterm. I see no reason why you see a
> difference.
When I run xterm on Ubuntu 18.04, I get an 8 color terminal. So, I'm
unable to reproduce the problem with xterm as well.
It's only in GNOME Terminal that I see the difference in color.
On Tue, May 14, 2019 at 11:57
Hi,
When converting test29 into a new style test, I came across several
instances where multiple lines of text need to be stored in a variable.
I used the following method to do it:
new
insert
some text
some text
some text
.
let text = getline(1, '$')
You can also use a list literal to st
Hi,
On Sat, May 11, 2019 at 10:12 AM Manuel Ortega wrote:
>
> On Friday, May 10, 2019 at 5:20:08 PM UTC-4, Bram Moolenaar wrote:
>
> > I think that's the best way we provide this functionality. But I like
> > to hear from others.
>
> I think this is adding complexity, a maintenance burden, and y
Am 30.03.2019 um 17:28 schrieb Bram Moolenaar:
Patch 8.1.1083
Problem:MS-Windows: hang when opening a file on network share.
Solution: Avoid using FindFirstFile(), use GetLongPathNameW(). (Ken Takata,
closes #3923)
Files: src/os_win32.c
Thanks for this one, very much app
Jason Franklin wrote:
> Thank you so much for taking the time to work with me on this.
>
> Unfortunately, I still can't get the colors to match on the latest build
> (patch 8.1.1330). I should note that the color scheme is much closer than
> it was before, but it looks like some of the colors
Patch 8.1.1331
Problem:Test 29 is old style.
Solution: Turn it into a new style test. (Yegappan Lakshmanan, closes #4370)
Files: src/Makefile, src/testdir/Make_all.mak, src/testdir/Make_vms.mms,
src/testdir/test29.in, src/testdir/test29.ok,
src/testdir/test_back
Ken Takata wrote:
> I also noticed that the colors on Cygwin + mintty with 256-color mode are
> wrong since 8.1.1146. Especially, yellow becomes brown.
> The following patch seems to fix the problem:
>
> --- a/src/terminal.c
> +++ b/src/terminal.c
> @@ -2432,6 +2432,8 @@ color2index(VTermColor
Thanks, Ken.
> The following patch seems to fix the problem:
It does fix the problem for me. With the patch applied, I can't tell the
difference in the output of "colors" in a Vim terminal window and in GNOME
Terminal directly.
However, it seems like this is a band-aid and not a real fix. Why
12 matches
Mail list logo