viluon / luaextended Goto Github PK

It seems that All Autocomplete clashes with LuaExtended's completions for the standard library.

I don't know if this is possible to fix easily.
Keep up the good work!

The new function scope merged from #9 seems to work great for functions, however my custom syntax pack no longer works as a result of the main scope not being used.

If a function definition precedes my class declaration, my syntax theme fails to pick it up - this is not the case with traditional Lua (hence I believe it is a LuaExtended issue, and not something I am doing incorrectly).

This is my syntax context:

  main:
    - match: "\\b(class|extends|mixin|alias)\\b"
      scope: keyword
      push: class-string-declaration

    - match: "\\b(abstract)\\b\\s+(?=class)\\b"
      scope: keyword

    - match: "\\b(configureConstructor)\\b(?=(\\w+))"
      scope: keyword

    - include: Packages/LuaExtended/LuaExtended.sublime-syntax

This does not work if a function is defined above the class declaration. Replacing 'LuaExtended' with 'Lua', fixes the issue but at the expense of losing the benefits of LuaExtended.

Screenshots:

Doesn't work

Does work

foo( something, something_else )

Will indent the following line one more tab (because of the else). This also holds for comments!

The GIF below was taken in a completely blank file, and the same keystrokes were used for both functions, however the result is... inconsistent.

The scope responsible for highlighting error strings matches with regular strings in the file if error is defined as a variable:

I have used re-indent on previously written lua file it did failed to indent properly elseif blocks and braces at times
So I used solution mentioned in this
it seems issue is in "Indent.tmPreferences" file I fixed it and working fine now.

We already have dfun, but what about drepeat or dfor? Programmers are all too often too lazy to comment their code on their own, this would mildly force them to do so (there's always the option to stick to the original snippets).

i install this package, but it not work.
does this plug can used on ubuntu?

Any newlines in the function definition will, while being correct syntactically, break the highlighting, because the regex is only matched against a single line. This means the function definition rule will have to be rewritten and split to form its own scope.

Hi there 👋. The base scope of this syntax is source.luae. The default syntax's base scope is source.lua. What are the differences between the two? Perhaps more to the point, is this syntax compatible with lua-language-server? https://github.com/sumneko/lua-language-server

I'm maintaining a helper package for that server here: https://github.com/sublimelsp/LSP-lua. It only accounts for the default syntax. If this package is indeed compatible with this language server:

• Should the syntax's base scope in this package be renamed to source.lua?
• Or should LSP-lua account for an additional base scope source.luae?

After installing and setting LuaExtended, SublimeLinter can not work properly and lose detection capability.

If the string inside of the error call is broken up via concatenation, the highlighting does not carry through:

Also, if the error call doesn't have parentheses around the string, it is not colored at all:

Sublime Text 3 snippets have the option to access the $SELECTION variable, making them suitable for transforming selected text. There are cases when you would like to convert a for loop to a while loop, for example. Would it be too hard to implement snippets for that?