You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
since 4.8.24-rc1 (4.8.23-149-g06bf088bc), the syntax highlighting of shell scripts in mcedit misbehaves around matches of "function blabla()" inside literal quotes. It applies syntax highlighting as if it was function definition in normal conditions (out of literal quotes), breaking the colouring of whatever follows.
The following sample shows the issue:
function foo()
{
echo "normal color highlighting"
echo "function bar() abnormal color highlighting"
}
The text was updated successfully, but these errors were encountered:
Changed by wwp (subscript@….fr) on Jan 21, 2020 at 12:48 UTC(comment 1)
Apparently, the default is NOT in sh.syntax, because replacing w/ 4.8.23's one doesn't fix it. If the code for syntax highlighthing in mcedit itself is fault, then it's probably buggy for some other languages.
Important
This issue was migrated from Trac:
wwp
(subscript@….fr)syntaxt
,highlighting
,shell
,mcedit
since 4.8.24-rc1 (4.8.23-149-g06bf088bc), the syntax highlighting of shell scripts in mcedit misbehaves around matches of "function blabla()" inside literal quotes. It applies syntax highlighting as if it was function definition in normal conditions (out of literal quotes), breaking the colouring of whatever follows.
The following sample shows the issue:
The text was updated successfully, but these errors were encountered: