Wrong highlighting on here-string (<<<)

[de-jcup]

text="a b c"
read a b c<<<"$text
echo $a $b $c  # actual code, no here-document!

is highlighted wrong:

see

• http://tldp.org/LDP/abs/html/x17837.html
• https://unix.stackexchange.com/questions/76402/command-line-instead-of
• https://www.gnu.org/software/bash/manual/bashref.html#Here-Strings
  for information

Origin information came from https://marketplace.eclipse.org/comment/5055#comment-5055

[de-jcup]

When and trying to execute the example script from above bash was not able to execut the script because having a failure inside (unexpected file end...). It seems that the script has got a failure because of wrong line:
read a b c<<<"$text
which should be replaced by:
read a b c<<<"$text"
so the double quoted string has to be closed. The highlighting comes not from a here-doc but the unclosed string.

[de-jcup]

Never the less the parser did have problems with determinating <<< as herestring instead of heredoc. This was fixed in last commit above.

[de-jcup]

Hello @themagican,
could you please look at the problem described above? In my opinion it is correct to handle the multiline string as multiline. I changed the test script to

text="a b c"
read a b c<<<"$text
echo $a $b $c  # actual code, no here-document!"
echo $a $b $c # this is really actual code
echo "Next echo statement..."

and got following:

I think this correct.

[atetzner]

IMHO the highlighting in the example above is correct: A here-string sets the STDIN for the command that is currently executed. The here-string can be given anywhere in the command line and does not need to be the last argument. As the bash-documentation states, the here-string is exacly one word so everything after the here-string is an additional parameter to the command.

I will extend the example from above to explain it in more detail:

text="a b c d"
read a b c <<< "$text
echo $a $b $c  # actual code, no here-document!" echo
echo $a $b $c $echo

This command

• Executes read
• Gives the parameters a b c and echo to read
• Sets the STDIN for read to be the above multi-line string

The relevant part here is, that echo is a parameter to read and is not a keyword. The result from the command above is, that the variables are a b and c are set to a b and c. An additional variable echo is created with the value d

(Actually the syntax highlighting in github is wrong, as the echo in line 3 above is highlighted as a keyword in blue)

A functional equivalent to the code above without using a here-string would be:

echo "$text
echo $a $b $c  # actual code, no here-document!" | read a b c echo

[de-jcup]

@themagican : Thank you!

[zeroincombenze]

Sorry, I posted a wrong example
This is th right code to replicate error

get_full_xtlcmd() {
    local xtlcmd=$(get_act_xtlcmd $2 "$1" "$3" "$4" "$5")
    local pkg lop lreqver p rop rreqver branch x pkgURL subpkg
    IFS="~" read pkg lop lreqver rop rreqver branch x<<<"$5"
    p=" $2"
    if [ "$2" == "EVERYTHINGS" ]; then
        p=""
    fi
    pkgURL=$(get_full_URL "$1" "$2" "$3" "$4" "$5")
    [ -n "$pkgURL" ] && p=" $pkgURL"

[zeroincombenze]

FYI,
in most pieces of bash code recognition works well