Syntax coloring behavior folllowing <<EOF in bash

[alexr00]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.79.1
• OS Version: Linux x64 5.19.0-38-generic

Following #177977 I still got some syntax error with cat<<EOF syntax in bash files

Steps to Reproduce:

The behavior change depending if you write:

#!/usr/bin/env bash

cat <<EOF | sudo tee myfile
{
    "jsonObject": {
        "key1": "value1",
        "key2": "value2"
    }
}
EOF

Or (simply remove the space between cat and <<EOF and this is a valid syntax):

#!/usr/bin/env bash

cat<<EOF | sudo tee myfile
{
    "jsonObject": {
        "key1": "value1",
        "key2": "value2"
    }
}
EOF

The expected behavior for me is:

• The context should be display as a pure string between the EOF mark and it is done well in the first exemple but not in the second.
• Depending on what is comming after cat<<EOF either a pipe or a redirect it should adapt the syntax color for command or string, it is well done in the second example but not in the first
• On previous version of vscode the EOF mark had special syntax differencing them from the rest of the text and I think it was a good things

There is some good things on both behavior but neither is perfect from my point of vue and it still make syntax coloring inconsistent.

Originally posted by @Arcahub in https://github.com/microsoft/vscode/issues/185119

[jeff-hykin]

Should be fixed as of v1.8.6

[punkyard]

hi if i get it right, the code in EOF blocks should be coloured? so far it isn't is this a bug?