You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I upgraded node from v5.7.0 to v6.1.0, I installed tern on v6.1.0 (globally). It works on v5.7.0, any idea? However, it works if I start the tern manually:
Start emacs
Open a javascript file
Autocomplete not working
I start the tern manually
Run tern-use-server and specify the port of the tern that I ran manually.
Autocomplete works fine
which tern
$HOME/.nvm/versions/node/v6.1.0/bin/tern
Reproduction guide
Start Emacs
Open a javascript file
Type a variable name
Press TAB, it will fail to show completion and there's a message Request failed: (nil)
Observed behaviour:
There's a message Request failed: (nil), I did check the tern process ps aux | grep tern, no tern process running.
Expected behaviour:
It should show completion list when I pressed TAB when I'm typing a variable name
Might be related to this problem. nodejs/node#6563
Open a shell in emacs and check if you can run node in it. You should get "Abort trap: 6 error ".
If so, then you have to upgrade Node to 6.2
Tern not running on node v6.1.0
I upgraded node from v5.7.0 to v6.1.0, I installed tern on v6.1.0 (globally). It works on v5.7.0, any idea? However, it works if I start the tern manually:
tern-use-server
and specify the port of the tern that I ran manually.Reproduction guide
TAB
, it will fail to show completion and there's a messageRequest failed: (nil)
Observed behaviour:
There's a message
Request failed: (nil)
, I did check the tern processps aux | grep tern
, no tern process running.Expected behaviour:
It should show completion list when I pressed
TAB
when I'm typing a variable nameSystem Info
(auto-completion elm emacs-lisp git go haskell html javascript markdown org osx php react restclient swift syntax-checking themes-megapack theming unimpaired version-control vim-empty-lines vim-powerline yaml)
Backtrace
The text was updated successfully, but these errors were encountered: