Hi Doug,

no, I haven't set the g:is_kornshell variable. If typing that as ex-command I'm 
getting: 
"E121: Undefined variable: g:is_kornshell".  Also if setting it in .vimrc 
there's no change.

Does that mean I have a too old vim installation, and with the next update it 
works?


Concerning the embedded Awk syntax... - I don't know what "heredoc markers" are.
But I was able to just recover the embedded awk add-on from an old backup file.
It's rather short; I paste it below...
Is that something that could be streamlined into the Vim distribution or shall 
these
things be kept individually and local under $HOME/.vim ?


"Sh: EMBEDDING LANGUAGES~
"You may wish to embed languages into sh.  I'll give an example courtesy of
"Lorance Stinson on how to do this with awk as an example. Put the following
"file into $HOME/.vim/after/syntax/sh/awkembed.vim:

" AWK Embedding: {{{1
" ==============
" Shamelessly ripped from aspperl.vim by Aaron Hope.
if exists("b:current_syntax")
    unlet b:current_syntax
endif
syn include @AWKScript syntax/awk.vim
syn region AWKScriptCode matchgroup=AWKCommand start=+[=\\]\@<!'+ skip=+\\'+ 
end=+'+ contains=@AWKScript contained
syn region AWKScriptEmbedded matchgroup=AWKCommand start=+\<awk\>+ skip=+\\$+ 
end=+[=\\]\@<!'+me=e-1 contains=@shIdList,@shExprList2 nextgroup=AWKScriptCode
syn cluster shCommandSubList add=AWKScriptEmbedded
hi def link AWKCommand Type

"This code will then let the awk code in the single quotes: >
"   awk '...awk code here...'
"be highlighted using the awk highlighting syntax.  Clearly this may be
"extended to other languages.




________________________________________
Von: [email protected] <[email protected]> im Auftrag von Doug 
Kearns <[email protected]>
Gesendet: Mittwoch, 13. Mai 2026 16:31
An: [email protected]
Betreff: Re: [vim/vim] runtime/syntax/sh.vim: Array highlighting (Issue #20183)

Hi Janis,

On Wed, 13 May 2026 at 23:48, Janis Papanagnou 
<[email protected]<mailto:[email protected]>> wrote:

<snip>

My question is whether newer versions of sh.vim are supporting these things,
whether it's on the radar, or whether someone is even already working on fixes
in that area?

I think, off the top of my head, that all of those features are supported.  
There's been quite a lot of work done on KornShell support in the last twelve 
months.

I suspect you haven't set the g:is_kornshell variable?  You can check by 
running :let g:is_kornshell which should return something like "g:is_kornshell 
#1" if it's set or an "undefined" message if not.

See :help ft-ksh-syntax for details.

Another question is whether highlighting of in Shell embedded Awk source code
could be officially supported. Someone once provided me with an add-on (that I
had put is some user directory beneath ~/.vim/ ) but that wasn't working 
correctly
in all respects and sadly that add-on also vanished with a system crash I had.

 No, it's not currently supported.  I don't know how your plugin used to do it 
but I assume it required specific heredoc markers?

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/CAJ1uvoA1%3DN0X5pVECM-MQDCa6Uniaru2J5g8YC%3D1v7v0ocH7bw%40mail.gmail.com<https://groups.google.com/d/msgid/vim_dev/CAJ1uvoA1%3DN0X5pVECM-MQDCa6Uniaru2J5g8YC%3D1v7v0ocH7bw%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/DU0PR02MB1042260422DE10A53470ACB90F3062%40DU0PR02MB10422.eurprd02.prod.outlook.com.

Raspunde prin e-mail lui