Hi,
Is there a reason that the Corona Editor plugin doesn’t differentiate words that are camelCased or separated by a “.”
For eksample,
Holding shift and ctrl to mark the text:
camelCase.index
I would want to only mark “camel”, then “Case” on the next arrow key press and “.index” on the third one.
I believe “vanilla” Sublime Text 2 and Lua Glider does this.
Is there an easy way to get this behavior with the Corona Editor?
Is there a reason that the Corona Editor plugin doesn’t differentiate words that are camelCased or separated by a “.”
We treat periods specially so we can complete things like display.newText properly (it only affects buffers editing files with .lua extensions). You can turn off this behavior by setting the user preference
corona\_sdk\_complete\_periods
to false (you’ll need to close and reopen any open files due to Sublime Text’s tenacious hold on certain preferences).
For eksample,
Holding shift and ctrl to mark the text:
camelCase.index
I would want to only mark “camel”, then “Case” on the next arrow key press and “.index” on the third one.I believe “vanilla” Sublime Text 2 and Lua Glider does this.
We haven’t changed the behavior of camel case in the Corona Editor plugin. I have to hold down both Ctrl and Alt with the arrow keys to move along the camel cased words but it works the same in .lua files and other files (this is on a Mac).
This StackOverflow post has a lot of info on how to change the default keys used by camel case navigation and is probably worth looking at.
Thank you for the answer. Pretty new to Sublime and key-binding preferences things. Will set to false :)
Would it be possible to hilight global variables? Is this possible now, only hindered by my ignorance?
Love the editor either way 
Especially “accidentally global variables”, right? We don’t have a solution for that yet but it’s the kind of thing we’d like to add.
In the meantime, you’ll find more than you ever wanted to know about the topic here http://lua-users.org/wiki/DetectingUndefinedVariables
Thanks! Keep the feedback coming.
Is there a reason that the Corona Editor plugin doesn’t differentiate words that are camelCased or separated by a “.”
We treat periods specially so we can complete things like display.newText properly (it only affects buffers editing files with .lua extensions). You can turn off this behavior by setting the user preference
corona\_sdk\_complete\_periods
to false (you’ll need to close and reopen any open files due to Sublime Text’s tenacious hold on certain preferences).
For eksample,
Holding shift and ctrl to mark the text:
camelCase.index
I would want to only mark “camel”, then “Case” on the next arrow key press and “.index” on the third one.I believe “vanilla” Sublime Text 2 and Lua Glider does this.
We haven’t changed the behavior of camel case in the Corona Editor plugin. I have to hold down both Ctrl and Alt with the arrow keys to move along the camel cased words but it works the same in .lua files and other files (this is on a Mac).
This StackOverflow post has a lot of info on how to change the default keys used by camel case navigation and is probably worth looking at.
Thank you for the answer. Pretty new to Sublime and key-binding preferences things. Will set to false :)
Would it be possible to hilight global variables? Is this possible now, only hindered by my ignorance?
Love the editor either way
Especially “accidentally global variables”, right? We don’t have a solution for that yet but it’s the kind of thing we’d like to add.
In the meantime, you’ll find more than you ever wanted to know about the topic here http://lua-users.org/wiki/DetectingUndefinedVariables
Thanks! Keep the feedback coming.