Repository navigation
Bug: URI in comment after shebang is syntax-highlighted until its argument. #23
Description
What type of issues are you dealing with?
Incorrect highlighting
What happened?
This applies even if the comment isn't indented.
Which text editors are you seeing the problem on?
VSCode
Include a code snippet
#!/usr/bin/env xdg-open
# https://learn.microsoft.com/en-us/search/?scope=Minecraft&view=minecraft-bedrock-stable&terms=shebang
effect give @e minecraft:speed 99999 255 true
# Gives all entities speed 255 for 99 999s.
Activity
beedell-roke commentedon Mar 6, 2025
It appears to reproduce on GitHub, too!
rx-dev commentedon Mar 6, 2025
Ah, this is due to
#!being considered for block comments.. A space between the first and second lines would break the block. I haven't seen#!bang comments being used for mcfunction, interestingrx-dev commentedon Mar 6, 2025
This might be Won't Fix but wondering if there are stronger opinions
beedell-roke commentedon Mar 7, 2025
@ritikshah, for a script file to be correctly interpretable as such in Linux-based OSes, especially when executable (
chmod +x), it requires a shebang at the start of the file, denoted with the#!syntax. ECMAScript nowadays supports this, 1 and Python has always supported it, so it's not uncommon. Havingxdg-openset as the default invoker allows it to be executable, but still be set to the OS or DE's default file-to-application association.Footnotes
github.com/tc39/proposal-hashbang↩rx-dev commentedon Apr 4, 2026
there's nothing to execute though?
Footnotes
github.com/tc39/proposal-hashbang↩beedell-roke commentedon Apr 4, 2026
@rx-dev, with
enable-rcon=true, it should be trivial to send to an active MC instance.