Hi Doug,
first, some recent (last 24 h) email from you (concerning sh) landed in my
spam folder and I'm unsure I recovered it correctly (or removed it). - Please
resend if you're missing some replies concerning your emails or need further
input from me. - Thanks.
Now, concerning your email message below...
I'm not sure what "ksh2020" is supposed to mean or identify . The original
standard ksh (based on original AT&T ksh) is ksh93 (either "ksh93u+" or the
maintained version "ksh93u+m" from Martijn Dekker).
It would be inappropriate to require a change in the shebang lines of scripts
to be all changed from "#!/bin/ksh" or "#!/bin/ksh93" to "#!/bin/ksh2020".
But I may as well have just misread your statement and all you wanted to say
is probably that "*if* I'm using that ksh2020 then I need to define the shebang
line accordingly".
The Vim solution should certainly be effective for all ksh versions;
specifically
for a generic "ksh" or "ksh93".
Concerning "incorrect paren error" you noticed; all the "Kornshell-patterns"
(that are in Bash called "extended patterns") should be verified, if you noticed
in one case a highlighting error with the parenthesis; @(...), *(...), +(...),
?(...), !(...),
and there's also the {n}(...} and {n,m}(...) variants (but I've never used the
latter).
Thanks.
Regards,
Janis
________________________________________
Von: [email protected] <[email protected]> im Auftrag von Doug
Kearns <[email protected]>
Gesendet: Freitag, 15. Mai 2026 17:01
An: [email protected]
Betreff: Re: [vim/vim] runtime/syntax/sh.vim: Array highlighting (Issue #20183)
On Fri, 15 May 2026 at 05:02, Janis Papanagnou
<[email protected]<mailto:[email protected]>> wrote:
Hi Doug,
I have no single test file so I list some ad hoc constructs that are still
wrongly
market as errors in my currently used 9.1 version...
a=${x/y}
b=${x/y/z}
c=${x//y/z}
d=${.sh.value}
set "${name}"+([0-9]).*
When highlighting ksh2020 (this currently requires a "#!/bin/ksh2020" shebang
line) those examples are highlighted correctly except for the last one that
contains an incorrect paren error. I'll try and fix it.
Regards,
Doug
--
--
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
[email protected]<mailto:[email protected]>.
To view this discussion visit
https://groups.google.com/d/msgid/vim_dev/CAJ1uvoAUtm0SHbfkF3PA-77MH0Fopx9hbnQZh_WhdjKr_%2Bi-Rw%40mail.gmail.com<https://groups.google.com/d/msgid/vim_dev/CAJ1uvoAUtm0SHbfkF3PA-77MH0Fopx9hbnQZh_WhdjKr_%2Bi-Rw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
--
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/vim_dev/DU0PR02MB10422815F2153242C37E61665F3042%40DU0PR02MB10422.eurprd02.prod.outlook.com.
