The syntax highlighting problems I've faced in the past are with syntaxes
that I can't limit to a specific part of a file, such as a markdown file
that has a code region in it. The problem syntaxes use the "extend" keyword
when they define a region. The "extend" keyword overrides the "keepend"
On Di, 16 Sep 2025, 'Björn Försterling' via vim_use wrote:
> Hello,
>
> I am wondering about the syntax group "bashAdminStatement" in
> "runtime/syntax/sh.vim".
> The syntax highlighting for these words seems unfitting.
>
> syn keyword bashAdminStatement daemon killall killproc nice reload re
Hello,
ok, I will look into it.
Regards
Björn
On Wed Sep 17, 2025 at 10:31 PM CEST, Christian Brabandt wrote:
> Hi,
> It's not only that, it's also that certain commands (ls cat chmod) are
> only highlighted, if this is a detected bash or ksh script. I think we
> should move those to just Sta
Hi,
It's not only that, it's also that certain commands (ls cat chmod) are
only highlighted, if this is a detected bash or ksh script. I think we
should move those to just Statements.
We don't have a shell runtime file maintainer anymore and I assume
changing this breaks some existing syntax t
Thank you for the answer.
The words "daemon", "reload", "restart", "start", "status", and "stop" are
neither bash keywords nor external commands.
Maybe they were implemented for init scripts, but these are hardly used
anymore today.
The words "killall", "killproc", and "nice" are external command
Hello,
I am wondering about the syntax group "bashAdminStatement" in
"runtime/syntax/sh.vim".
The syntax highlighting for these words seems unfitting.
syn keyword bashAdminStatement daemon killall killproc nice reload restart
start status stop
Maybe these were designed for init scripts or syst
