Re: locally failing test_vim9_builtin
On 23/09/10 10:31 AM, Christian Brabandt wrote: On So, 10 Sep 2023, Ernie Rael wrote: If I run a shell script unset DISPLAY make test_vim9_builtin The error does not occur. Thanks. This, explains (I'm waving my hands) that when doing `make test_vim9_builtin` some random gvim pops up to the foreground. Out of curiosity, I'll look at Test_remote_expr (or at least put it on a todo list) since I have no idea what feature I'm unfamiliar with is being tested. It is using the remote expression feature, that only works with a X11 server. Not clear why it doesn't work correctly in your case. Are you possibly using Wayland instead? Not wayland. I'm running a vanilla System76 popOS $ env|grep XDG_SESSION XDG_SESSION_DESKTOP=pop XDG_SESSION_TYPE=x11 XDG_SESSION_CLASS=user Executing from the default console (I guess xterm is long gone), ps has /usr/bin/gnome-terminal.real plus hundreds of other things. -ernie I usually don't run the tests in a X11 session, so I don't know if there is something wrong with the test (or your Environment). Thanks, Christian -- -- 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 information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/b78b6345-754d-903a-4d97-828b9b63973e%40raelity.com.
Re: locally failing test_vim9_builtin
On So, 10 Sep 2023, Ernie Rael wrote: > If I run a shell script > >unset DISPLAY >make test_vim9_builtin > > The error does not occur. Thanks. > > This, explains (I'm waving my hands) that when doing `make > test_vim9_builtin` some random gvim pops up to the foreground. Out of > curiosity, I'll look at Test_remote_expr (or at least put it on a todo list) > since I have no idea what feature I'm unfamiliar with is being tested. It is using the remote expression feature, that only works with a X11 server. Not clear why it doesn't work correctly in your case. Are you possibly using Wayland instead? I usually don't run the tests in a X11 session, so I don't know if there is something wrong with the test (or your Environment). Thanks, Christian -- Old Grandad is dead but his spirits live on. -- -- 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 information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/ZP39Wfag31Pc4ddm%40256bit.org.
Commit: patch 9.0.1894: CI: trailing whitespace in tests
patch 9.0.1894: CI: trailing whitespace in tests
Commit:
https://github.com/vim/vim/commit/e5f7cd0a60d0eeab84f7aeb35c13d3af7e50072e
Author: Christian Brabandt
Date: Sun Sep 10 19:25:26 2023 +0200
patch 9.0.1894: CI: trailing whitespace in tests
Problem: CI: trailing white space in tests
Solution: clean up the trailing white space
Signed-off-by: Christian Brabandt
diff --git a/src/testdir/test_functions.vim b/src/testdir/test_functions.vim
index 2ed7eb7f7..2cc57163d 100644
--- a/src/testdir/test_functions.vim
+++ b/src/testdir/test_functions.vim
@@ -315,7 +315,7 @@ func Test_strptime()
call assert_fails('call strptime()', 'E119:')
call assert_fails('call strptime("xxx")', 'E119:')
- " This fails on BSD 14 and returns
+ " This fails on BSD 14 and returns
" -2209078800 instead of 0
call assert_equal(0, strptime("%Y", ''))
call assert_equal(0, strptime("%Y", "xxx"))
diff --git a/src/testdir/test_vim9_builtin.vim
b/src/testdir/test_vim9_builtin.vim
index 0d246a242..c793da6b4 100644
--- a/src/testdir/test_vim9_builtin.vim
+++ b/src/testdir/test_vim9_builtin.vim
@@ -4348,7 +4348,7 @@ def Test_strptime()
v9.CheckDefAndScriptFailure(['strptime(10, "2021")'], ['E1013: Argument 1:
type mismatch, expected string but got number', 'E1174: String required for
argument 1'])
v9.CheckDefAndScriptFailure(['strptime("%Y", 2021)'], ['E1013: Argument 2:
type mismatch, expected string but got number', 'E1174: String required for
argument 2'])
assert_notequal(0, strptime('%Y', '2021'))
-# This fails on BSD 14 and returns
+# This fails on BSD 14 and returns
# -2209078800 instead of 0
assert_equal(0, strptime('%Y', ''))
endif
diff --git a/src/version.c b/src/version.c
index ba7ea3970..d37d14721 100644
--- a/src/version.c
+++ b/src/version.c
@@ -699,6 +699,8 @@ static char *(features[]) =
static int included_patches[] =
{ /* Add new patch number below this line */
+/**/
+1894,
/**/
1893,
/**/
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/E1qfOG2-006Ony-Pl%40256bit.org.
Re: locally failing test_vim9_builtin
On 23/09/10 9:51 AM, Christian Brabandt wrote: On Sa, 09 Sep 2023, Ernie Rael wrote: Hi all, I'll often do: make $(ls test_vim9*.vim | sed 's/\.vim$//' | grep -v vim9_builtin) I need to exclude test_vim9_builtin because I typically get the errors, see below. Any idea on what's going on? -ernie Found errors in Test_remote_expr(): Not sure how you run it, I do make test_vim9_builtin If I run a shell script unset DISPLAY make test_vim9_builtin The error does not occur. Thanks. This, explains (I'm waving my hands) that when doing `make test_vim9_builtin` some random gvim pops up to the foreground. Out of curiosity, I'll look at Test_remote_expr (or at least put it on a todo list) since I have no idea what feature I'm unfamiliar with is being tested. -ernie but it seems Vim cannot connect to another Vim Server. Perhaps trying unsetting $DISPLAY (or not running it in your X11 session). Best, Christian -- -- 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 information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/0af6f70c-26ed-ad48-9e4f-302854e7216b%40raelity.com.
Commit: patch 9.0.1893: CI: strptime test fails on BSD14
patch 9.0.1893: CI: strptime test fails on BSD14
Commit:
https://github.com/vim/vim/commit/983d808674f998eaea12b302028de45f1c6857cd
Author: Christian Brabandt
Date: Sun Sep 10 19:06:09 2023 +0200
patch 9.0.1893: CI: strptime test fails on BSD14
Problem: CI: strptime test fails on BSD14
Solution: Skip the test
Signed-off-by: Christian Brabandt
diff --git a/src/testdir/test_functions.vim b/src/testdir/test_functions.vim
index b14c5413f..2ed7eb7f7 100644
--- a/src/testdir/test_functions.vim
+++ b/src/testdir/test_functions.vim
@@ -300,6 +300,7 @@ endfunc
func Test_strptime()
CheckFunction strptime
+ CheckNotBSD
if exists('$TZ')
let tz = $TZ
@@ -314,6 +315,8 @@ func Test_strptime()
call assert_fails('call strptime()', 'E119:')
call assert_fails('call strptime("xxx")', 'E119:')
+ " This fails on BSD 14 and returns
+ " -2209078800 instead of 0
call assert_equal(0, strptime("%Y", ''))
call assert_equal(0, strptime("%Y", "xxx"))
diff --git a/src/testdir/test_vim9_builtin.vim
b/src/testdir/test_vim9_builtin.vim
index dc5f3362b..0d246a242 100644
--- a/src/testdir/test_vim9_builtin.vim
+++ b/src/testdir/test_vim9_builtin.vim
@@ -4343,10 +4343,13 @@ enddef
def Test_strptime()
CheckFunction strptime
+ CheckNotBSD
if exists_compiled('*strptime')
v9.CheckDefAndScriptFailure(['strptime(10, "2021")'], ['E1013: Argument 1:
type mismatch, expected string but got number', 'E1174: String required for
argument 1'])
v9.CheckDefAndScriptFailure(['strptime("%Y", 2021)'], ['E1013: Argument 2:
type mismatch, expected string but got number', 'E1174: String required for
argument 2'])
assert_notequal(0, strptime('%Y', '2021'))
+# This fails on BSD 14 and returns
+# -2209078800 instead of 0
assert_equal(0, strptime('%Y', ''))
endif
enddef
diff --git a/src/version.c b/src/version.c
index 40f7fe944..ba7ea3970 100644
--- a/src/version.c
+++ b/src/version.c
@@ -699,6 +699,8 @@ static char *(features[]) =
static int included_patches[] =
{ /* Add new patch number below this line */
+/**/
+1893,
/**/
1892,
/**/
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/E1qfO1W-006NoB-W5%40256bit.org.
Re: IMPORTANT: Certificate for www.vim.org has expired.
On So, 10 Sep 2023, Marvin Renich wrote: > This is very odd. Is www.vim.org served by multiple hosts behind a load > balancer? > > When this was first reported yesterday, I went there and didn't have a > problem. I looked at the certificate, and it was issued 2023-08-26, > valid until 2023-11-24. > > When I went there just now, I received the security warning due to an > expired certificate. I refreshed the page (without accepting the > security exception), and I didn't have any trouble, and got the same > new certificate that I saw yesterday. > > The certificate is issued by Let's Encrypt, so the update is likely > handled automatically. If a load balancer is being used, perhaps the > updated certificate is not being propagated to all hosts. Oh that is true, I remember I checked the cert some time ago. It might be caused by OSDN. Yet another reason to migrate away :) I am currently in the process to plan the move, we should have a better hosting provider soon. I have already tested the vim php homepage with PHP 9 and it works. We just need to migrate the database and perform the switch once the server is ready (and I need to sync with the DNS admins to plan this). I hope to have news on this more during the week. Thanks, Christian -- Some men are so interested in their wives' continued happiness that they hire detectives to find out the reason for it. -- -- 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 information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/ZP347B9LLTEbmjkd%40256bit.org.
Re: IMPORTANT: Certificate for www.vim.org has expired.
* Christian Brabandt [230910 12:49]: > Hi, > thanks. I wasn't aware of this. I need to find out who used to manage > the SSL Certs. I am afraid this was done by Bram. May take a while until > this get's resolved :( > > Thanks, > Chris > > On Sa, 09 Sep 2023, Paul wrote: > > > PLEASE DO NOT CLICK ON ANYTHING IN THIS EMAIL THAT RENDERS AS A LINK. > > > > That said, this is nothing to panic about. However, the www.vim.org > > certificate appears to have expired at Fri, 08 Sep 2023 04:38:42 GMT. > > > > I am posting this to alert to the community and those in a position to work > > on fixing the problem. > > > > It is unlikely, but possible that the certificate is OK and I am a victim, > > hence do not trust any link in this email and do not hit your client's > > replay button. This is very odd. Is www.vim.org served by multiple hosts behind a load balancer? When this was first reported yesterday, I went there and didn't have a problem. I looked at the certificate, and it was issued 2023-08-26, valid until 2023-11-24. When I went there just now, I received the security warning due to an expired certificate. I refreshed the page (without accepting the security exception), and I didn't have any trouble, and got the same new certificate that I saw yesterday. The certificate is issued by Let's Encrypt, so the update is likely handled automatically. If a load balancer is being used, perhaps the updated certificate is not being propagated to all hosts. ...Marvin -- -- 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 information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/ZP33ZGl9/jO/Kv68%40basil.wdw.
Re: locally failing test_vim9_builtin
On Sa, 09 Sep 2023, Ernie Rael wrote:
> Hi all,
>
> I'll often do:
>
>make $(ls test_vim9*.vim | sed 's/\.vim$//' | grep -v vim9_builtin)
>
> I need to exclude test_vim9_builtin because I typically get the errors, see
> below. Any idea on what's going on?
>
> -ernie
>
> Abbreviating the errors so maybe it will get passed by the google groups
> filter
>
> Found errors in Test_remote_expr():
> [...]Expected 'E241: Unable to send to ' but got 'E449: Invalid expression
> received'
> [...]Test_remote_foreground line 8: command did not fail:
> remote_foreground("")
> Found errors in Test_remote_send():
Not sure how you run it, but it seems Vim cannot connect to another Vim
Server. Perhaps trying unsetting $DISPLAY (or not running it in your X11
session).
Best,
Christian
--
Is he the MAGIC INCA carrying a FROG on his shoulders?? Is the FROG
his GUIDELIGHT?? It is curious that a DOG runs already on the ESCALATOR ...
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/ZP30Kw9nfUXJCibU%40256bit.org.
Re: IMPORTANT: Certificate for www.vim.org has expired.
Hi, thanks. I wasn't aware of this. I need to find out who used to manage the SSL Certs. I am afraid this was done by Bram. May take a while until this get's resolved :( Thanks, Chris On Sa, 09 Sep 2023, Paul wrote: > PLEASE DO NOT CLICK ON ANYTHING IN THIS EMAIL THAT RENDERS AS A LINK. > > That said, this is nothing to panic about. However, the www.vim.org > certificate appears to have expired at Fri, 08 Sep 2023 04:38:42 GMT. > > I am posting this to alert to the community and those in a position to work > on fixing the problem. > > It is unlikely, but possible that the certificate is OK and I am a victim, > hence do not trust any link in this email and do not hit your client's > replay button. > Mit freundlichen Grüßen Christian -- The mosquito exists to keep the mighty humble. -- -- 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 information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/ZP3zm%2B4bZGrjj3rS%40256bit.org.
Commit: patch 9.0.1892: CI: no FreeBSD 14 support
patch 9.0.1892: CI: no FreeBSD 14 support
Commit:
https://github.com/vim/vim/commit/24a95f42b8469944a1e74838438ac8f1d86f9450
Author: Philip H <47042125+pheid...@users.noreply.github.com>
Date: Sun Sep 10 18:31:51 2023 +0200
patch 9.0.1892: CI: no FreeBSD 14 support
Problem: CI: no FreeBSD 14 support
Solution: Drop support for FreeBSD 12, add FreeBSD 14
closes: #13059
Signed-off-by: Christian Brabandt
Co-authored-by: Philip H <47042125+pheid...@users.noreply.github.com>
diff --git a/.cirrus.yml b/.cirrus.yml
index cfe1d8e38..7ea83f53a 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -5,12 +5,12 @@ env:
freebsd_task:
name: FreeBSD
matrix:
-- name: FreeBSD 13.1
+- name: FreeBSD 14.0
freebsd_instance:
-image_family: freebsd-13-1
-- name: FreeBSD 12.4
+image_family: freebsd-14-0
+- name: FreeBSD 13.1
freebsd_instance:
-image_family: freebsd-12-4
+image_family: freebsd-13-1
timeout_in: 20m
install_script:
- pkg install -y gettext
diff --git a/src/version.c b/src/version.c
index faeabfa6c..40f7fe944 100644
--- a/src/version.c
+++ b/src/version.c
@@ -699,6 +699,8 @@ static char *(features[]) =
static int included_patches[] =
{ /* Add new patch number below this line */
+/**/
+1892,
/**/
1891,
/**/
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/E1qfNYV-006Leu-OX%40256bit.org.
Commit: runtime(masm): add support for AVX-2 and AVX-512 (#13061)
runtime(masm): add support for AVX-2 and AVX-512 (#13061)
Commit:
https://github.com/vim/vim/commit/e7833e73471a110c7c38c80935e1b840f254a3da
Author: Wu Yongwei
Date: Mon Sep 11 00:27:31 2023 +0800
runtime(masm): add support for AVX-2 and AVX-512
(https://github.com/vim/vim/issues/13061)
Signed-off-by: Christian Brabandt
diff --git a/runtime/syntax/masm.vim b/runtime/syntax/masm.vim
index 3be0fd45d..85e457106 100644
--- a/runtime/syntax/masm.vim
+++ b/runtime/syntax/masm.vim
@@ -2,7 +2,7 @@
" Language:Microsoft Macro Assembler (80x86)
" Orig Author: Rob Brady
" Maintainer: Wu Yongwei
-" Last Change: 2022-04-24 20:07:04 +0800
+" Last Change: 2023-09-09 20:48:26 +0800
" Quit when a syntax file was already loaded
if exists("b:current_syntax")
@@ -194,8 +194,8 @@ syn keyword masmRegisterR8W R9W R10W R11W R12W R13W
R14W R15W
syn keyword masmRegister R8B R9B R10B R11B R12B R13B R14B R15B
" SSE/AVX registers
-syn match masmRegister "\(X\|Y\)MM[0-9]\>"
-syn match masmRegister "\(X\|Y\)MM1[0-5]\>"
+syn match masmRegister "\(X\|Y\|Z\)MM[12]\?[0-9]\>"
+syn match masmRegister "\(X\|Y\|Z\)MM3[01]\>"
" Instruction prefixes
syn keyword masmOpcode LOCK REP REPE REPNE REPNZ REPZ
@@ -338,11 +338,192 @@ syn keyword masmOpcode VINSERTF128
VEXTRACTF128 VMASKMOVPS VMASKMOVPD
syn keyword masmOpcode VPERMILPS VPERMILPD VPERM2F128
syn keyword masmOpcode VZEROALL VZEROUPPER
+" AVX-2 (Haswell and later)
+syn keyword masmOpcode VPBROADCASTB VPBROADCASTW VPBROADCASTD
+syn keyword masmOpcode VPBROADCASTQ VBROADCASTI128
+syn keyword masmOpcode VINSERTI128 VEXTRACTI128
+syn keyword masmOpcode VGATHERDPD VGATHERQPD VGATHERDPS VGATHERQPS
+syn keyword masmOpcode VPGATHERDD VPGATHERDQ VPGATHERQD VPGATHERQQ
+syn keyword masmOpcode VPMASKMOVD VPMASKMOVQ
+syn keyword masmOpcode PERMPS VPERMD VPERMPD VPERMQ VPERM2I128
+syn keyword masmOpcode VPBLENDD VPSLLVD VPSLLVQ VPSRLVD VPSRLVQ
+syn keyword masmOpcode VPSRAVD
+
+" AVX-512 (Knights Landing/Skylake-X and later)
+syn keyword masmOpcode KAND KANDN KMOV KUNPCK KNOT KOR KORTEST
+syn keyword masmOpcode KSHIFTL KSHIFTR KXNOR KXOR KADD KTEST
+syn keyword masmOpcode VBLENDMPD VBLENDMPS
+syn keyword masmOpcode VPBLENDMD VPBLENDMQ VPBLENDMB VPBLENDMW
+syn keyword masmOpcode VPCMPD VPCMPUD VPCMPQ VPCMPUQ
+syn keyword masmOpcode VPCMPB VPCMPUB VPCMPW VPCMPUW
+syn keyword masmOpcode VPTESTMD VPTESTMQ VPTESTNMD VPTESTNMQ
+syn keyword masmOpcode VPTESTMB VPTESTMW VPTESTNMB VPTESTNMW
+syn keyword masmOpcode VCOMPRESSPD VCOMPRESSPS VPCOMPRESSD VPCOMPRESSQ
+syn keyword masmOpcode VEXPANDPD VEXPANDPS VPEXPANDD VPEXPANDQ
+syn keyword masmOpcode VPERMB VPERMW VPERMT2B VPERMT2W VPERMI2PD
+syn keyword masmOpcode VPERMI2PS VPERMI2D VPERMI2Q VPERMI2B VPERMI2W
+syn keyword masmOpcode VPERMT2PS VPERMT2PD VPERMT2D VPERMT2Q
+syn keyword masmOpcode VSHUFF32x4 VSHUFF64x2 VSHUFI32x4 VSHUFI64x2
+syn keyword masmOpcode VPMULTISHIFTQB VPTERNLOGD VPTERNLOGQ
+syn keyword masmOpcode VPMOVQD VPMOVSQD VPMOVUSQD VPMOVQW VPMOVSQW
+syn keyword masmOpcode VPMOVUSQW VPMOVQB VPMOVSQB VPMOVUSQB VPMOVDW
+syn keyword masmOpcode VPMOVSDW VPMOVUSDW VPMOVDB VPMOVSDB VPMOVUSDB
+syn keyword masmOpcode VPMOVWB VPMOVSWB VPMOVUSWB
+syn keyword masmOpcode VCVTPS2UDQ VCVTPD2UDQ VCVTTPS2UDQ VCVTTPD2UDQ
+syn keyword masmOpcode VCVTSS2USI VCVTSD2USI VCVTTSS2USI VCVTTSD2USI
+syn keyword masmOpcode VCVTPS2QQ VCVTPD2QQ VCVTPS2UQQ VCVTPD2UQQ
+syn keyword masmOpcode VCVTTPS2QQ VCVTTPD2QQ VCVTTPS2UQQ VCVTTPD2UQQ
+syn keyword masmOpcode VCVTUDQ2PS VCVTUDQ2PD VCVTUSI2PS VCVTUSI2PD
+syn keyword masmOpcode VCVTUSI2SD VCVTUSI2SS VCVTUQQ2PS VCVTUQQ2PD
+syn keyword masmOpcode VCVTQQ2PD VCVTQQ2PS VGETEXPPD
+syn keyword masmOpcode VGETEXPPS VGETEXPSD VGETEXPSS
+syn keyword masmOpcode VGETMANTPD VGETMANTPS VGETMANTSD VGETMANTSS
+syn keyword masmOpcode VFIXUPIMMPD VFIXUPIMMPS VFIXUPIMMSD VFIXUPIMMSS
+syn keyword masmOpcode VRCP14PD VRCP14PS VRCP14SD VRCP14SS
+syn keyword masmOpcode VRNDSCALEPS VRNDSCALEPD VRNDSCALESS VRNDSCALESD
+syn keyword masmOpcode VRSQRT14PD VRSQRT14PS VRSQRT14SD VRSQRT14SS
+syn keyword masmOpcode VSCALEFPS VSCALEFPD VSCALEFSS VSCALEFSD
+syn keyword masmOpcode VBROADCASTI32X2 VBROADCASTI32X4 VBROADCASTI32X8
+syn keyword masmOpcode VBROADCASTI64X2 VBROADCASTI64X4
+syn keyword masmOpcode VALIGND VALIGNQ VDBPSADBW VPABSQ VPMAXSQ
+syn keyword masmOpcode VPMAXUQ VPMINSQ VPMINUQ VPROLD VPROLVD VPROLQ
+syn keyword masmOpcode VPROLVQ VPRORD VPRORVD VPRORQ VPRORVQ
+syn keyword masmOpcode VPSCATTERDD VPSCATTERDQ VPSCATTERQD VPSCATTERQQ
+syn keyword masmOpcode
Commit: patch 9.0.1891: No runtime support for Mojo
patch 9.0.1891: No runtime support for Mojo
Commit:
https://github.com/vim/vim/commit/0ce2c594d0704f27a16d2c13fce85d596cc91489
Author: Mahmoud Abduljawad
Date: Sun Sep 10 18:23:04 2023 +0200
patch 9.0.1891: No runtime support for Mojo
Problem: No runtime support for Mojo
Solution: Add basic filetype and syntax plugins
closes: #13062
closes: #13063
Signed-off-by: Christian Brabandt
Signed-off-by: Doug Kearns
Co-authored-by: Mahmoud Abduljawad
diff --git a/runtime/filetype.vim b/runtime/filetype.vim
index 81764c1b5..9b7e698c2 100644
--- a/runtime/filetype.vim
+++ b/runtime/filetype.vim
@@ -1368,6 +1368,10 @@ au BufNewFile,BufRead *.rc,*.rch
\ setf rc |
\ endif
+" Mojo
+" Mojo files use either .mojo or .🔥 as extension
+au BufNewFile,BufRead *.mojo,*.🔥 setf mojo
+
" MuPAD source
au BufRead,BufNewFile *.mu setf mupad
diff --git a/runtime/syntax/mojo.vim b/runtime/syntax/mojo.vim
new file mode 100644
index 0..b7dae24a1
--- /dev/null
+++ b/runtime/syntax/mojo.vim
@@ -0,0 +1,316 @@
+" Vim syntax file
+" Language:Mojo
+" Maintainer: Mahmoud Abduljawad
+" Last Change: 2023 Sep 09
+" Credits: Mahmoud Abduljawad
+" Neil Schemenauer
+" Dmitry Vasiliev
+"
+" This is based on Vim Python highlighting
+"
+" - introduced highlighting of doctests
+" - updated keywords, built-ins, and exceptions
+" - corrected regular expressions for
+"
+"* functions
+"* decorators
+"* strings
+"* escapes
+"* numbers
+"* space error
+"
+" - corrected synchronization
+" - more highlighting is ON by default, except
+" - space error highlighting is OFF by default
+"
+" Optional highlighting can be controlled using these variables.
+"
+" let mojo_no_builtin_highlight = 1
+" let mojo_no_doctest_code_highlight = 1
+" let mojo_no_doctest_highlight = 1
+" let mojo_no_exception_highlight = 1
+" let mojo_no_number_highlight = 1
+" let mojo_space_error_highlight = 1
+"
+" All the options above can be switched on together.
+"
+" let mojo_highlight_all = 1
+"
+" The use of Python 2 compatible syntax highlighting can be enforced.
+" The straddling code (Python 2 and 3 compatible), up to Python 3.5,
+" will be also supported.
+"
+" let mojo_use_python2_syntax = 1
+"
+" This option will exclude all modern Python 3.6 or higher features.
+"
+
+" quit when a syntax file was already loaded.
+if exists("b:current_syntax")
+ finish
+endif
+
+" We need nocompatible mode in order to continue lines with backslashes.
+" Original setting will be restored.
+let s:cpo_save = &cpo
+set cpo&vim
+
+if exists("mojo_no_doctest_highlight")
+ let mojo_no_doctest_code_highlight = 1
+endif
+
+if exists("mojo_highlight_all")
+ if exists("mojo_no_builtin_highlight")
+unlet mojo_no_builtin_highlight
+ endif
+ if exists("mojo_no_doctest_code_highlight")
+unlet mojo_no_doctest_code_highlight
+ endif
+ if exists("mojo_no_doctest_highlight")
+unlet mojo_no_doctest_highlight
+ endif
+ if exists("mojo_no_exception_highlight")
+unlet mojo_no_exception_highlight
+ endif
+ if exists("mojo_no_number_highlight")
+unlet mojo_no_number_highlight
+ endif
+ let mojo_space_error_highlight = 1
+endif
+
+" These keywords are based on Python syntax highlight, and adds to it struct,
+" fn, alias, var, let
+"
+syn keyword mojoStatement False None True
+syn keyword mojoStatement as assert break continue del global
+syn keyword mojoStatement lambda nonlocal pass return with yield
+syn keyword mojoStatement class def nextgroup=mojoFunction skipwhite
+syn keyword mojoStatement struct fn nextgroup=mojoFunction skipwhite
+syn keyword mojoStatement alias var let
+syn keyword mojoConditionalelif else if
+syn keyword mojoRepeat for while
+syn keyword mojoOperator and in is not or
+syn keyword mojoException except finally raise try
+syn keyword mojoIncludefrom import
+syn keyword mojoAsync async await
+
+" Soft keywords
+" These keywords do not mean anything unless used in the right context.
+" See https://docs.python.org/3/reference/lexical_analysis.html#soft-keywords
+" for more on this.
+syn match mojoConditional "^\s*\zscase\%(\s\+.*:.*$\)\@="
+syn match mojoConditional "^\s*\zsmatch\%(\s\+.*:\s*\%(#.*\)\=$\)\@="
+
+" Decorators
+" A dot must be allowed because of @MyClass.myfunc decorators.
+syn match mojoDecorator "@" display contained
+syn match mojoDecoratorName "@\s*\h\%(\w\|\.\)*" display
contains=pythonDecorator
+
+" Python 3.5 introduced the use of the same symbol for matrix multiplication:
+" https://www.python.org/dev/peps/pep-0465/. We now have to exclude the
+" symbol from highlighting when used in that context
Commit: patch 9.0.1890: Vim9: lookup code for class/object repaeated
patch 9.0.1890: Vim9: lookup code for class/object repaeated
Commit:
https://github.com/vim/vim/commit/f36bbcd402c6ee5a27bcab3b20b6362ab93b8898
Author: Yegappan Lakshmanan
Date: Sun Sep 10 18:19:06 2023 +0200
patch 9.0.1890: Vim9: lookup code for class/object repaeated
Problem: Vim9: lookup code for class/object repaeated
Solution: Refactor and make use of lookup functions
closes: #13067
Signed-off-by: Christian Brabandt
Co-authored-by: Yegappan Lakshmanan
diff --git a/src/eval.c b/src/eval.c
index ec8d3baf9..dd7b8d8f3 100644
--- a/src/eval.c
+++ b/src/eval.c
@@ -1540,71 +1540,57 @@ get_lval(
// round 1: class functions (skipped for an object)
// round 2: object methods
for (int round = v_type == VAR_OBJECT ? 2 : 1;
- round <= 2; ++round)
+ round <= 2; ++round)
{
- int count = round == 1
- ? cl->class_class_function_count
- : cl->class_obj_method_count;
- ufunc_T **funcs = round == 1
- ? cl->class_class_functions
- : cl->class_obj_methods;
- for (int i = 0; i < count; ++i)
+ int m_idx;
+ ufunc_T *fp;
+
+ fp = method_lookup(cl,
+ round == 1 ? VAR_CLASS : VAR_OBJECT,
+ key, p - key, &m_idx);
+ if (fp != NULL)
{
- ufunc_T *fp = funcs[i];
- char_u *ufname = (char_u *)fp->uf_name;
- if (STRNCMP(ufname, key, p - key) == 0
-&& ufname[p - key] == NUL)
- {
- lp->ll_ufunc = fp;
- lp->ll_valtype = fp->uf_func_type;
- round = 3;
- break;
- }
+ lp->ll_ufunc = fp;
+ lp->ll_valtype = fp->uf_func_type;
+ break;
}
}
}
if (lp->ll_valtype == NULL)
{
- int count = v_type == VAR_OBJECT
- ? cl->class_obj_member_count
- : cl->class_class_member_count;
- ocmember_T *members = v_type == VAR_OBJECT
- ? cl->class_obj_members
- : cl->class_class_members;
- for (int i = 0; i < count; ++i)
+ int m_idx;
+ ocmember_T *om;
+
+ om = member_lookup(cl, v_type, key, p - key, &m_idx);
+ if (om != NULL)
{
- ocmember_T *om = members + i;
- if (STRNCMP(om->ocm_name, key, p - key) == 0
- && om->ocm_name[p - key] == NUL)
+ switch (om->ocm_access)
{
- switch (om->ocm_access)
- {
- case VIM_ACCESS_PRIVATE:
-
semsg(_(e_cannot_access_private_member_str),
-om->ocm_name);
- return NULL;
- case VIM_ACCESS_READ:
- if ((flags & GLV_READ_ONLY) == 0)
- {
-
semsg(_(e_member_is_not_writable_str),
-om->ocm_name);
- return NULL;
- }
- break;
- case VIM_ACCESS_ALL:
- break;
- }
-
- lp->ll_valtype = om->ocm_type;
-
- if (v_type == VAR_OBJECT)
- lp->ll_tv = ((typval_T *)(
- lp->ll_tv->vval.v_object + 1)) + i;
- else
- lp->ll_tv = &cl->class_members_tv[i];
- break;
+ case VIM_ACCESS_PRIVATE:
+ semsg(_(e_cannot_access_privat
Commit: runtime(scala): Fix Scala highlighting string literal as type param (#13070)
runtime(scala): Fix Scala highlighting string literal as type param (#13070)
Commit:
https://github.com/vim/vim/commit/066103307534f81de08a092aac3a15e864a5a25f
Author: Emil Ejbyfeldt
Date: Sun Sep 10 18:16:51 2023 +0200
runtime(scala): Fix Scala highlighting string literal as type param
(https://github.com/vim/vim/issues/13070)
Since https://docs.scala-lang.org/sips/42.type.html which is implemented
in Scala 2.13 and in Scala 3 it possible to use string literals as
singleton types. So code like
```
someFunc["abc"]
```
is valid. Currently this code is not hightlighted correctly and worse if
there is an unclosed `(` in the string it breaks the formating in the
rest of the file.
I also submitted this patch to the mentioned project for this runtime
file: https://github.com/derekwyatt/vim-scala/pull/173 But there are no
commits there over the last 2 years and no response in the week since I
created it. Also the last change to the Scala syntax file:
https://github.com/vim/vim/pull/9594 is yet to be backported to that
repo. Therefore I am opening this PR as well to get some feedback on how
to proceed to get this fixed.
Signed-off-by: Christian Brabandt
diff --git a/runtime/syntax/scala.vim b/runtime/syntax/scala.vim
index c08e60e55..cc098ce01 100644
--- a/runtime/syntax/scala.vim
+++ b/runtime/syntax/scala.vim
@@ -180,7 +180,7 @@ hi def link scalaNumber Number
syn region scalaRoundBrackets start="(" end=")" skipwhite contained
contains=scalaTypeDeclaration,scalaSquareBrackets,scalaRoundBrackets
-syn region scalaSquareBrackets matchgroup=scalaSquareBracketsBrackets
start="\[" end="\]" skipwhite nextgroup=scalaTypeExtension
contains=scalaTypeDeclaration,scalaSquareBrackets,scalaTypeOperator,scalaTypeAnnotationParameter
+syn region scalaSquareBrackets matchgroup=scalaSquareBracketsBrackets
start="\[" end="\]" skipwhite nextgroup=scalaTypeExtension
contains=scalaTypeDeclaration,scalaSquareBrackets,scalaTypeOperator,scalaTypeAnnotationParameter,scalaString
syn match scalaTypeOperator /[-+=:<>]\+/ contained
syn match scalaTypeAnnotationParameter /@\<[`_A-Za-z0-9$]\+\>/ contained
hi def link scalaSquareBracketsBrackets Type
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/E1qfNJz-006Kbc-KR%40256bit.org.
Commit: patch 9.0.1889: Vim9 static tests fail
patch 9.0.1889: Vim9 static tests fail
Commit:
https://github.com/vim/vim/commit/0405405536f06a3bf384757be4affa9c1a07bdcd
Author: Yegappan Lakshmanan
Date: Sun Sep 10 18:12:56 2023 +0200
patch 9.0.1889: Vim9 static tests fail
Problem: Vim9 static tests fail
Solution: Fix tests, make CI happy ;)
closes: #13064
Signed-off-by: Christian Brabandt
Co-authored-by: Yegappan Lakshmanan
diff --git a/src/testdir/test_vim9_disassemble.vim
b/src/testdir/test_vim9_disassemble.vim
index c918bf6b1..540fd55fa 100644
--- a/src/testdir/test_vim9_disassemble.vim
+++ b/src/testdir/test_vim9_disassemble.vim
@@ -3067,17 +3067,13 @@ def Test_disassemble_interface_static_member()
def F1(i: I)
var x: number
- x = i.s_var
x = i.o_var
- x = i.s_var2
x = i.o_var2
enddef
def F2(o: C)
var x: number
- x = o.s_var
x = o.o_var
- x = o.s_var2
x = o.o_var2
enddef
@@ -3087,43 +3083,27 @@ def Test_disassemble_interface_static_member()
v9.CheckScriptSuccess(lines)
assert_match('\d*_F1\_s*' ..
'var x: number\_s*' ..
-'x = i.s_var\_s*' ..
+'x = i.o_var\_s*' ..
'0 LOAD arg\[-1\]\_s*' ..
-'1 ITF_MEMBER 0 on I \[STATIC\]\_s*' ..
+'1 ITF_MEMBER 0 on I\_s*' ..
'2 STORE $0\_s*' ..
-'x = i.o_var\_s*' ..
+'x = i.o_var2\_s*' ..
'3 LOAD arg\[-1\]\_s*' ..
-'4 ITF_MEMBER 0 on I\_s*' ..
+'4 ITF_MEMBER 1 on I\_s*' ..
'5 STORE $0\_s*' ..
-'x = i.s_var2\_s*' ..
-'6 LOAD arg\[-1\]\_s*' ..
-'7 ITF_MEMBER 1 on I \[STATIC\]\_s*' ..
-'8 STORE $0\_s*' ..
-'x = i.o_var2\_s*' ..
-'9 LOAD arg\[-1\]\_s*' ..
-'10 ITF_MEMBER 1 on I\_s*' ..
-'11 STORE $0\_s*' ..
-'12 RETURN void\_s*',
+'6 RETURN void\_s*',
g:instr1)
assert_match('\d*_F2\_s*' ..
'var x: number\_s*' ..
-'x = o.s_var\_s*' ..
+'x = o.o_var\_s*' ..
'0 LOAD arg\[-1\]\_s*' ..
-'1 OBJ_MEMBER 0 \[STATIC\]\_s*' ..
+'1 OBJ_MEMBER 0\_s*' ..
'2 STORE $0\_s*' ..
-'x = o.o_var\_s*' ..
+'x = o.o_var2\_s*' ..
'3 LOAD arg\[-1\]\_s*' ..
-'4 OBJ_MEMBER 0\_s*' ..
+'4 OBJ_MEMBER 1\_s*' ..
'5 STORE $0\_s*' ..
-'x = o.s_var2\_s*' ..
-'6 LOAD arg\[-1\]\_s*' ..
-'7 OBJ_MEMBER 1 \[STATIC\]\_s*' ..
-' 8 STORE $0\_s*' ..
-'x = o.o_var2\_s*' ..
-'9 LOAD arg\[-1\]\_s*' ..
-'10 OBJ_MEMBER 1\_s*' ..
-'11 STORE $0\_s*' ..
-'12 RETURN void',
+'6 RETURN void',
g:instr2)
unlet g:instr1
diff --git a/src/version.c b/src/version.c
index d3be87cb0..11bf957d5 100644
--- a/src/version.c
+++ b/src/version.c
@@ -699,6 +699,8 @@ static char *(features[]) =
static int included_patches[] =
{ /* Add new patch number below this line */
+/**/
+1889,
/**/
1888,
/**/
--
--
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 information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/E1qfN5W-006JVM-J0%40256bit.org.
