Double click selecting whole term, instead of 1 word (not detecting '.').

Solar2D Corona Editor
#1

Hi there,

First of all - I read README and change 

"corona\_sdk\_complete\_periods": false

If you haven’t done that - it’s your best bet.

If you have done that but your sublime keeps selecting whole term here is what happened to me, maybe it helps. I just spent 1 hour fixing it (reinstalling sublime/plugin, etc…).

I saved a project at one point. And inside the project ( projectname.sublime-workspace ) file there is a line like this:

"word\_separators": "/\\()\"'-:,;\<\>~!@#$%^&\*|+=[]{}`~?"

I am guessing that because I saved my project before switching the flag “corona_sdk_complete_periods”, project also saved incorrect word separators. There is a ‘.’ missing. It should be:

"word\_separators": "./\\()\"'-:,.;\<\>~!@#$%^&\*|+=[]{}`~?",

Anyway, hope this helps anyone.

Thanks,

Kreso

#2

I guess this was wishful thinking on my part. The problem still persists - and it’s driving me crazy.

I have no clue why this happens.

Is there anyone else using Sublime Text 3 and treating your files as a Project? Have you managed to have this annoying option disabled?

Thank you in advance!

Kreso

#3

I find it annoying too but since its not my main editor I didn’t investigate further when turning it off did not do the trick.

I remember another thread about this, here it is: http://forums.coronalabs.com/topic/43563-corona-editor-selecting-period/

Have you checked it?

#4

Thanks for your reply!!

I just found this: http://forums.coronalabs.com/topic/42364-setting-preferences-in-corona-editor-10/

Basically it says Corona editor isn’t really working like it says it does in the README, that jumps up when you install Corona editor into Sublime first time. No clue why the README wouldn’t be changed to reflect this, but I guess that is a story for some other day…

Corona Editor wasn’t my first choice either - I used Glider but I seem to be experiencing unsolvable/untraceable bug that me and other total of 13 users of netbeans experience - which disallows me to work in it.

#5

The current version of Corona Editor has some issues with the word_separators, though I think a fix for it is on the way. Because Sublime’s docs are so sparse I’ve only been able to make educated guesses at what the issues are, but I’ve created my own fork of the project for now that seems to work fine (for me) without the word_separators issue.

You can find it here. You just need to clone it into your Sublime Packages folder. https://github.com/personalnadir/CoronaSDK-SublimeText

#6

Thanks a bunch tap32!

For now, I followed instruction to put the “corona_sdk_complete_periods” flag into Sublime-Settings-User like suggested here.

Hopefully it keeps on working. 

#7

I guess this was wishful thinking on my part. The problem still persists - and it’s driving me crazy.

I have no clue why this happens.

Is there anyone else using Sublime Text 3 and treating your files as a Project? Have you managed to have this annoying option disabled?

Thank you in advance!

Kreso

#8

I find it annoying too but since its not my main editor I didn’t investigate further when turning it off did not do the trick.

I remember another thread about this, here it is: http://forums.coronalabs.com/topic/43563-corona-editor-selecting-period/

Have you checked it?

#9

Thanks for your reply!!

I just found this: http://forums.coronalabs.com/topic/42364-setting-preferences-in-corona-editor-10/

Basically it says Corona editor isn’t really working like it says it does in the README, that jumps up when you install Corona editor into Sublime first time. No clue why the README wouldn’t be changed to reflect this, but I guess that is a story for some other day…

Corona Editor wasn’t my first choice either - I used Glider but I seem to be experiencing unsolvable/untraceable bug that me and other total of 13 users of netbeans experience - which disallows me to work in it.

#10

The current version of Corona Editor has some issues with the word_separators, though I think a fix for it is on the way. Because Sublime’s docs are so sparse I’ve only been able to make educated guesses at what the issues are, but I’ve created my own fork of the project for now that seems to work fine (for me) without the word_separators issue.

You can find it here. You just need to clone it into your Sublime Packages folder. https://github.com/personalnadir/CoronaSDK-SublimeText

#11

Thanks a bunch tap32!

For now, I followed instruction to put the “corona_sdk_complete_periods” flag into Sublime-Settings-User like suggested here.

Hopefully it keeps on working.