Bug: URI in comment after shebang is syntax-highlighted until its argument.

[RokeJulianLockhart]

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.

[RokeJulianLockhart]

#23 (comment)

It appears to reproduce on GitHub, too!

[rx-dev]

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, interesting

[rx-dev]

This might be Won't Fix but wondering if there are stronger opinions

[RokeJulianLockhart]

#23 (comment)

@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, ¹ and Python has always supported it, so it's not uncommon. Having xdg-open set 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

1. github.com/tc39/proposal-hashbang ↩