Thank you, that's where I'm going as well.
On Sunday, September 3, 2023 at 9:04:47 PM UTC+3 Doug Kearns wrote:
> 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
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
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
