profile stop and profile dump show the sub command stop and dump as an error. I took a look at the source, but I've never worked with syntax-hl and quickly stopped looking.

includes

@  changeset:   174:46ddce48cfe9
|  bookmark:    main
|  tag:         default/main
|  tag:         tip
|  user:        lagygoill <[email protected]>
|  date:        Sun May 22 21:03:29 2022 +0200
|  summary:     support bitwise shift operators

@lacygoill (since I don't know if you monitor these issues)

errorformat can be quite long. So I often split it across multiple lines. I've noticed that this isn't supported yet.

Example:

vim9script

CompilerSet errorformat=
        \%D%*\\a[%*\\d]:\ Entering\ directory\ %*[`']%f',
        \%X%*\\a[%*\\d]:\ Leaving\ directory\ %*[`']%f',
        \%D%*\\a:\ Entering\ directory\ %*[`']%f',
        \%X%*\\a:\ Leaving\ directory\ %*[`']%f'

I have quite a few motion mappings similar to the following:

vim9script
# Jump to next/previous git conflict marker
nnoremap ]x <scriptcmd>mark `<bar>range(v:count1)->map((_, _) => search('^\(<\\|=\\|>\)\{7}\([^=].\+\)\?$', 'W'))<cr>
nnoremap [x <scriptcmd>mark `<bar>range(v:count1)->map((_, _) => search('^\(<\\|=\\|>\)\{7}\([^=].\+\)\?$', 'bW'))<cr>
xnoremap ]x <scriptcmd>mark `<bar>range(v:count1)->map((_, _) => search('^\(<\\|=\\|>\)\{7}\([^=].\+\)\?$', 'W'))<cr>
xnoremap [x <scriptcmd>mark `<bar>range(v:count1)->map((_, _) => search('^\(<\\|=\\|>\)\{7}\([^=].\+\)\?$', 'bW'))<cr>

Unfortunately, after the mark the syntax file highlights some parts of the RHS as vim9MarkCmdArgInvalid.

Screenshot:

Adding a ` to mark_valid fixes the issue, but only if we also add a whitespace before the <bar>:

diff --git a/import/vim9Language.vim b/import/vim9Language.vim
index 7f5e6aa..cd0d56b 100644
--- a/import/vim9Language.vim
+++ b/import/vim9Language.vim
@@ -1472,7 +1472,7 @@ export const logical_not: string = '/\w\@1<!![~=]\@!!*/'

 # mark_valid {{{1

-export const mark_valid: string = '[a-zA-Z''[\]<>0-9"^.(){}]'
+export const mark_valid: string = '[a-zA-Z`''[\]<>0-9"^.(){}]'

 # maybe_dict_literal_key {{{1

An improvement would be to add <bar> to the regex in the syntax match vim9MarkCmdArg, but I don't know if you want to further complicate the regex:

diff --git a/syntax/vim.vim b/syntax/vim.vim
index f0288c8..1ef0ca0 100644
--- a/syntax/vim.vim
+++ b/syntax/vim.vim
@@ -1511,7 +1511,7 @@ syntax keyword vim9MarkCmd ma[rk]
     \ skipwhite

 syntax match vim9MarkCmdArgInvalid /[^ \t|]\+/ contained
-execute 'syntax match vim9MarkCmdArg /\s\@1<=' .. lang.mark_valid .. '\_s\@=/ contained'
+execute 'syntax match vim9MarkCmdArg /\s\@1<=' .. lang.mark_valid .. '\%(\_s\|<bar>\)\@=/ contained'

 # :nnoremap {{{3

Some of the command-completion attributes are highlighted as a syntax error. Example:

vim9script

command -nargs=+ -complete=filetype      Test1 echo <q-args>
command -nargs=+ -complete=file          Test2 echo <q-args>
command -nargs=+ -complete=file_in_path  Test3 echo <q-args>
command -nargs=+ -complete=tag           Test4 echo <q-args>
command -nargs=+ -complete=tag_listfiles Test5 echo <q-args>

Screenshot:

This is because the longer attributes are short-circuited in the regex they are defined in. The order matters. Longer names should be defined first.

The following patch fixes the issue:

diff --git a/import/vim9Language.vim b/import/vim9Language.vim
index 7f5e6aa..fabd880 100644
--- a/import/vim9Language.vim
+++ b/import/vim9Language.vim
@@ -628,9 +628,9 @@ const command_complete_type_list: list<string> =<< trim END
     environment
     event
     expression
-    file
-    file_in_path
     filetype
+    file_in_path
+    file
     function
     help
     highlight
@@ -647,8 +647,8 @@ const command_complete_type_list: list<string> =<< trim END
     sign
     syntax
     syntime
-    tag
     tag_listfiles
+    tag
     user
     var
 END

Result:

I looked at a build based on today's release and don't see vim9-syntax in there. I looked prompted by #13047 (which you commented on).

Is there a reason this isn't available. I'd be very unhappy if I wasn't using it.

I'd like to try this, stumbled across this and I've been unhappy with vim9 syntax highlighting...

Had to look up vim stuff to install, seems to be working. Thanks. the lambdas were the worst, they look good now.

The README for tools is out of date, and I figure I don't need to run the Generator script.

Many thanks.