`do.sublime-snippet` doesn't work as expected

[ghost]

The snippet sublime-text-lsl / snippets / commons / do.sublime-snippet doesn't have the desired effect. The problem is in line 4 where it says:

<snippet>
<content><![CDATA[do$LSL_SPACE_OR_NEWLINE{
$0;
}$LSL_SPACE_OR_NEWLINEwhile (${1:condition});]]></content>
<tabTrigger>do</tabTrigger>
<scope>meta.function.body.lsl, meta.event.body.lsl, meta.function.body.ossl, meta.event.body.ossl</scope>
<description>flow control</description>
</snippet>

$LSL_SPACE_OR_NEWLINEwhile is being ignored because it's an unknown tag.

[Makopo]

It works on my osx environment. Please tell your environment - operation systems and versions. Thanks.

[ghost]

I'm on Windows 7 x64 Ultimate with Sublime 3059 stable.

Output on my editor is either:

do
{
    $0;
} (${1:condition});

or

do {
    $0;
} (${1:condition});

As you can see the first $LSL_SPACE_OR_NEWLINE is being read correctly. The second is being ignored though as well as the while, probably because it's being read as $LSL_SPACE_OR_NEWLINEwhile which isn't defined.

[Makopo]

I confirmed the issue in the current version. Unfortunately there seems to be no way to completely fix this issue. To avoid the non-compilable case, I added a space before the variable for now. a7e383a1781462c849f1ebd270235e1abc3ef688

[FichteFoll]

Does ${LSL_SPACE_OR_NEWLINE}while work?

[Makopo]

@FichteFoll Thanks! It works now!

[ghost]

Nice catch!

[buildersbrewery]

Hi Mako,

FYI ${LSL_SPACE_OR_NEWLINE} works in *.sublime-completions files as well. You can merge the snippet files into one completions file.

[buildersbrewery]

However you'll need to set a default indent style when loading the LSL package, because setting it in the __init__ of ChangeStyleCommand is too late.

Compare:

https://github.com/buildersbrewery/linden-scripting-language/tree/master/sublimetext/LSL