Open ForNeVeR opened 9 years ago
Hm, maybe it will be better to install all packages and automatically disable some of them?
I also think package-sync should save the enable/disable state of the package. In fact, because it didn't I had to manually disable certain packages afterwards. These packages were disabled on the original machine.
Yes that's a good idea.
Consider that I'm using
haskell-ghc-mod
package and I own multiple machines.Not all of my machines have
ghc-mod
installed, so I don't want to installhaskell-ghc-mod
on all of them (because it throws errors if installed in a wrong environment). But I'd still like to storehaskell-ghc-mod
in mypackages.cson
file so I can install it only on the proper machines. I don't want it to be automatically blindly installed when I callpackage-sync:sync
.One solution I see is to have a single
packages.cson
for all machines but some programmatic control over it (so, for example, I'd have filtered mypackages.cson
in myinit.coffee
based on the machine name or something like that).So, well, basically I'm requesting programmatic control over loading and saving
packages.cson
file via plugin API or some other options to deal with this use case.