search

tststs / atom-ternjs

JavaScript code intelligence for atom with tern.js and autocomplete-plus
MIT License
627 stars 76 forks source link

don't delete existing third party plugins #33

Open serkandurusoy opened 9 years ago

serkandurusoy commented 9 years ago

I'm using https://github.com/Slava/tern-meteor by dropping in meteor.js into ~/.atom/packages/atom-ternjs/node_modules/tern/plugin/ but every time atom-ternjs gets an update, the external plugin file gets deleted and I get to place it there once more.

Is it possible you replace only internal plugins and not touch the third party ones on update?

Or rather than copying over 3rd party plugins, there may perhaps be a setting somewhere we can add outside locations for atom-tern to look for existince of them.

tststs commented 9 years ago

I think this is related to atom itself. Every time the package is updated, atom cleans the directory and performs a fresh apm install for the package. I don' think there is any way to keep old files in that directory. But that's just speculation from my site :D

But i will have a look definitely. :)

thx tststs

serkandurusoy commented 9 years ago

Hmm, then, do you think it is possible to:

Or rather than copying over 3rd party plugins, there may perhaps be a setting somewhere we can add outside locations for atom-tern to look for existince of them.

ShaharHD commented 9 years ago

I think this issue is also discussed in #79