[Omni complete] Missing autocomplete for `Foo.` about tern_for_vim

[albertosantini]

You should add a .tern-project file containing node plugin.

For instance,

{
  "libs": [
    "browser",
    "yui"
  ],
  "plugins": {
      "node": {}
  }
}

See also the documentation:
http://ternjs.net/doc/manual.html#plugins

[oyvindkinsey]

We don't have any issues loading modules.
On May 18, 2013 11:00 PM, "albertosantini" [email protected] wrote:

You should add a .tern-project file containing node plugin.

For instance,

{
"libs": [
"browser",
"yui"
],
"plugins": {
"node": {}
}
}

See also the documentation:
http://ternjs.net/doc/manual.html#plugins

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-18112897
.

[oyvindkinsey]

We have multiple custom plugins, for loading and type annotation, so the
project file is all dandy :)
On May 18, 2013 11:03 PM, "Øyvind Sean Kinsey" [email protected] wrote:

We don't have any issues loading modules.
On May 18, 2013 11:00 PM, "albertosantini" [email protected]
wrote:

You should add a .tern-project file containing node plugin.

For instance,

{
"libs": [
"browser",
"yui"
],
"plugins": {
"node": {}
}
}

See also the documentation:
http://ternjs.net/doc/manual.html#plugins

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-18112897
.

[marijnh]

should in this case be treated as show me any available properties, something which works perfectly with locally defined types.

By default, Tern will only show any available properties when at least two characters have been given. These come from the cx.props registry, which is kept with no regard to origin file, so I don't see a reason for this to break for properties from different files. Are you sure you're comparing apples to apples? (I.e. does it really work for local properties when you don't type anything after the dot?)