Skip to content
This repository has been archived by the owner on Oct 20, 2022. It is now read-only.

strange behaviour autocomplete #17

Open
gritworks opened this issue May 14, 2013 · 2 comments
Open

strange behaviour autocomplete #17

gritworks opened this issue May 14, 2013 · 2 comments

Comments

@gritworks
Copy link

  • loading typescript plugin keeps spinning forever.
  • when i make a new class with a public function autocomplete doesn't seem to find it. restarting sublimetext sometimes solves the issue.

ST 2.01 build 2217
osx 10.7.5

How can i start the phyton console and see any error loggings in ST2?

@raph-amiard
Copy link
Owner

You probably have a configuration problem. Check the Sublime Text documentation to see how to open the python console, and check other issues here to see if anybody didn't have the same problem as yours. If you can't find anything, try and copy paste the log you have in the python console here.

@gritworks
Copy link
Author

installed on windows following the exact instructions. Produces the exact same result as my mac.

functions from within another class are not propagated in the autocomplete within, say, Main class. only (sometimes) after quitting and restarting sublimetext.

reference path from Main.ts is set to Test.ts

also strange behaviour is when i explicitly type out a property following a dot i get different results then autocompleting with tab and then typing a dot.

I could find anybody having the same issue so i guess i overlooked something very important.

not sure how to solve this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants