BBEdit/Textwrangler LCM for livescript
pete at lcsql.com
Sun Sep 6 21:18:14 CEST 2015
Thanks for this James.
I'm new to using TextWrangler but it appears that it doesn't recognize
multiple words in a keyword definition. For example "open file" isn't
colored as a keyword, only "file" because it has a separate keyword
definition. Not sure if there is a way round this other than breaking the
multiple word keywords into separate keyword definitions.
I would also like to learn how to define if/end if, repeat/end repeat, etc
as structures that can be folded. I tried using the Open Statement Blocks
and Close Statement Blocks keys in the plist to define "if" and "end" as a
statement block but they weren't recognized as foldable.
There are a number of other things that don't seem to be working as far as
colorization. Strings enclosed in quotes and variables aren't colored per
the Preferences settings, and keywords within quote-delimited strings are
colorized but shouldn't be. I tried using the Open Strings 1 and Close
Strings 1 set to quote but that had no effect.
On Sun, Sep 6, 2015 at 7:36 AM James Hale <james at thehales.id.au> wrote:
> I have modified Trevor's BBedit language module for livescript to bring it
> up to date with the current docs.
> (At least within the limitations of the language modules themselves.)
> It is now a Codeless Language Module and should work with the current
> version of these editors.
> I have tried it for BBedit and am assuming it will work for TextWrangler
> You can get it here
> https://dl.dropboxusercontent.com/u/8212901/Livescript.plist <
> Please note I haven't added the newer features available in BBEdit V11 as
> apart from working them out it would take a bit more extensive editing of
> all the keywords. If I give it a go I will post the update.
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode