4 errors on bad FTD, both N++ and FT breaks

[erinata]

4 errors on bad FTD, both N++ and FT breaks

[erinata]

First of all, I must say that I really like the idea of a convention-driven repository of snippets.

However, I never expect someone to edit the ftd file themselves. (That's why I didn't notice this bug I think)

But I need some time to look for the error. I can replicate the bug and I think it's due to the loose coding of how to deal with the [>END<] so that it cannot process [>$[![END]!]<] properly.

At this point of time I cannot think of an easy way to do what you want to do. But I will try to fix this bug and also think of a better way to let people do this convention-driven repository of snippets more easily.

[zyrolasting]

Allowing for multiple scopes in an FTD file would be a great first step. I cannot type, say, Lang:HTML|Lang:PHP on one line in an FTD file. I can only do that in the Snippet Editor. Outside of N++, I have to copy the snippet for each scope.

Imagine if you want to use Ext: for scopes that Lang: could not support. If the language you wanted to use Ext: for had multiple file extensions, then you have to copy the snippet once for each extension.

If you were running a repository with many users and thousands of snips, this one feature can significantly reduce disk usage and maintenance work.

[zyrolasting]

I just noticed something. I had similar weird behavior when I tried to use a normal .ftd file that did not have another .ftd file embedded in it. I compared what FingerText exports to what I am importing, and I found out that my lines closing snippets contained [>END<]$[FingerTextData FingerTextData]@#, which is incorrect because it lacks an exclamation point before the $. The correct string is [>END<]!$[FingerTextData FingerTextData]@#

That being said, look at the very last line of the sample I gave you in the OP.

On a side note, I also sent you an email about the repo.