-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
coffee-script doestn't auto complete #5896
Comments
Yes, there's no company backend for coffeescript. If you find one, do let us know. |
When I M-x invoke company-mode in coffee file, it realy works. So I think company-mode has support it, we just need to enable it? |
You're getting the basic autocompletion then, I believe, not semantic. Not sure how useful that is, since it's pretty straightforward and knows nothing of the language you're writing. |
If you write coffeescript,you will know it is useful. |
We can add company to the coffeescript hook then. |
Cool @syl20bnr |
On the latest develop, I see company-disabled with coffescript by default. How do I add it to the coffeescript hook like you mentioned @syl20bnr ? Or should it already be enabled by default and I'm seeing a bug? I tried adding |
@JuanCaicedo let me know if #8365 fixes your problem. To check out my branch execute the following commands: cd ~/.emacs.d
git remote add sdwolf https://github.com/sdwolf/spacemacs.git
git fetch sdwolf feature/coffee-dumb-autocomplete
git checkout feature/coffee-dumb-autocomplete |
@SDWolf Thanks for the step by step instructions! I'll comment on your PR |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
Description
CoffeeScript doesn't auto complete
Reproduction guide
Observed behaviour:
doesn't have auto completion support
Expected behaviour:
has auto completion support
System Info
(auto-completion emacs-lisp javascript git markdown react org clojure yaml)
Backtrace
The text was updated successfully, but these errors were encountered: