patch 9.0.1860: CI: test_crash1() is flaky
Commit:
https://github.com/vim/vim/commit/f44cbe96fa44d10d6dd717e0a9f6ef0f104ee98a
Author: Christian Brabandt
Date: Mon Sep 4 07:42:27 2023 +0200
patch 9.0.1860: CI: test_crash1() is flaky
Problem: CI: test_crash1() is flaky
patch 9.0.1859: heap-use-after-free in bt_normal()
Commit:
https://github.com/vim/vim/commit/6e60cf444a8839ca1694319bf9a82e7b097e5c4d
Author: Christian Brabandt
Date: Sun Sep 3 21:43:46 2023 +0200
patch 9.0.1859: heap-use-after-free in bt_normal()
Problem: heap-use-after-free
On So, 03 Sep 2023, Yegappan Lakshmanan wrote:
> On Sun, Sep 3, 2023 at 11:30 AM Christian Brabandt wrote:
> >
> > patch 9.0.1857: [security] heap-use-after-free in is_qf_win()
> >
> > Commit:
> > https://github.com/vim/vim/commit/fc68299d436cf87453e432daa77b6d545df4d7ed
> > Author: Christian
patch 9.0.1858: [security] heap use after free in ins_compl_get_exp()
Commit:
https://github.com/vim/vim/commit/ee9166eb3b41846661a39b662dc7ebe8b5e15139
Author: Christian Brabandt
Date: Sun Sep 3 21:24:33 2023 +0200
patch 9.0.1858: [security] heap use after free in ins_compl_get_exp()
Hi Christian,
On Sun, Sep 3, 2023 at 11:30 AM Christian Brabandt wrote:
>
> patch 9.0.1857: [security] heap-use-after-free in is_qf_win()
>
> Commit:
> https://github.com/vim/vim/commit/fc68299d436cf87453e432daa77b6d545df4d7ed
> Author: Christian Brabandt
> Date: Sun Sep 3 20:20:52 2023
patch 9.0.1857: [security] heap-use-after-free in is_qf_win()
Commit:
https://github.com/vim/vim/commit/fc68299d436cf87453e432daa77b6d545df4d7ed
Author: Christian Brabandt
Date: Sun Sep 3 20:20:52 2023 +0200
patch 9.0.1857: [security] heap-use-after-free in is_qf_win()
Problem:
G'day Ron,
On Sun, 3 Sept 2023 at 22:33, Ron Aaron wrote:
> I was just given a bug report for a new version of my syntax file, and
> the problem is that a syntax keyword with a lone '[' doesn't work (it
> causes an error message E789)
>
> I have 'syn iskeyword 33-255' (because everything
patch 9.0.1856: issues with formatting positional arguments
Commit:
https://github.com/vim/vim/commit/aa90d4f031f73a34aaef5746931ea746849a2231
Author: Christ van Willegen
Date: Sun Sep 3 17:22:37 2023 +0200
patch 9.0.1856: issues with formatting positional arguments
Problem:
patch 9.0.1855: mode() doesn't indicate command line for terminal
Commit:
https://github.com/vim/vim/commit/71ebf3bacaa22c841d9a8cb050c52fb21ac0970a
Author: h-east
Date: Sun Sep 3 17:12:55 2023 +0200
patch 9.0.1855: mode() doesn't indicate command line for terminal
Problem:
Thank you; I didn't know that about the 'optional tail'. So my 'fix'
actually means that both SQL and SQL[ will be recognized as keywords, which
isn't what's wanted.
The user who pointed out the issue is actually using 'neovim', so it would
be great (for me) if a solution which worked with the
On Sun, Sep 03, 2023 at 05:33:22AM -0700, Ron Aaron wrote:
> I was just given a bug report for a new version of my syntax file, and the
> problem is that a syntax keyword with a lone '[' doesn't work (it causes an
> error message E789)
See ":help E789":
<
Hmm. This works:SQL[[]
However, a keyword like exec[] if I try exec[[]] complains about the
trailing ]
I would have expected syntax keywords to be matched "as is" and not like
regexes.
On Sunday, September 3, 2023 at 3:33:22 PM UTC+3 Ron Aaron wrote:
> I was just given a bug report for
I was just given a bug report for a new version of my syntax file, and the
problem is that a syntax keyword with a lone '[' doesn't work (it causes an
error message E789)
I have 'syn iskeyword 33-255' (because everything except a space is a valid
keyword identifier) but the syntax parser in
patch 9.0.1854: test_crash1() fails on CI
Commit:
https://github.com/vim/vim/commit/db510ca8052884fd260f425025bacf44f6c92fa9
Author: Christian Brabandt
Date: Sun Sep 3 09:23:12 2023 +0200
patch 9.0.1854: test_crash1() fails on CI
Problem: test_crash1() fails on CI
Solution:
On So, 03 Sep 2023, Adri Verhoef wrote:
> Originally, I reported this back in 2018. Since then, the documentation for
> job_start() moved from eval.txt to channel.txt and the text that I'm
> describing is still there.
>
> In the documentation for job_start() it shows:
>
> On
On Sa, 02 Sep 2023, Ernie Rael wrote:
> New problem? Or is it just me?
No I noticed it too. It was my attempt to ensure the security fixes are
correctly tested and do no longer crash vim. But it seems Screendump
tests do not work well for that. I have a different test now, will be
pushing
16 matches
Mail list logo