AirCode doesn't like block comments

Aircode does not like --[[ ]]-- comments. If they’re in your code, any code that occurs after they close will not be highlighted with the proper syntax highlighting. it’ll all appear as comments.

This is with the latest version of Codea, using AirCode inside Chrome.

the ending of a block comment should be --]] and not ]]--. Maybe that is the pb?

yup, that fixed it! Thanks! derp derp on my part!

It’s still odd that ]] followed by – would result in all text following the --'s would be formatted as comments

i am not sure it is odd. ‘[[ … ]]’ is one big text bloc (with multiple line returns allowed).
So ‘–[[ … ]]’ is: comment this text bloc.
then ‘–[[ … ]]-- xxx’ is: comment this ‘–[[ … ]]’ then comment that ‘-- xxx’.
This could be the logic.

@Jmv38 You’re correct, it works like that --[[ comment here ]] end of comment, the two dashes at the end don’t make a difference to the block comment but that line after it.

Just an update that AirCode still doesn’t like block comments at the top of a file.

paste this code here into a tab and open it in AirCode, you’ll see what I mean:

http://codea.io/talk/discussion/2806/long-press-event-detection/p1

On my mac, the same problem.

I add comment to the code:

for i,v in pairs(box) do
      --print("box."..i.."="..v)
      print(v)
end

Pic before block comment:

Pic after block comment:

This problem still exists @luatee @simeon

@matkatmusic Codea hasn’t received an update yet, why did you assume it was fixed?

@matkatmusis I have the same problem with air code. I’d avoid using it till its farther on in development. Theres lot of other problems that make it hard to seriously try to use it for any duration.

@matkatmusic I don’t use Air Code so I can’t try this. But the block comment below also works in Codea. Does it work in Air Code. The ending --]] doesn’t require the --.


--[[
some code
]]