-
Notifications
You must be signed in to change notification settings - Fork 71
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
cannot get anything to work #459
Comments
Yes it should work fine. Are there any error messages? Which version of atom are you running? If there are JSON errors in .remote-sync.json, it will not load the package, however it currently leaves the menu options in the the context menu, they just do nothing, like you're describing. If this were the case however, it would have displayed a large error message within Atom at launch. You could try putting nothing but |
I get the following error: Failed to require the main module of 'remote-sync' because it requires one or more incompatible native modules (fsevents, binding, binding, binding, binding, binding, binding). I ran apm rebuild in /Users/mike/.atom/packages/remote-sync and I still get the same issue |
Which versions of Atom / Remote Sync are you using? |
I tried in atom 1.22.0 I also updated OSX recently to latest version |
remote-sync 4.1.8 [email protected] – Cannot find module '/Users/mike/.atom/packages/remote-sync/node_modules/fsevents/lib/binding/Release/electron-v1.6-darwin-x64/fse.node' |
Just what I was about to mention... apm can get into a bit of a tizzy, it seems, if it has been upgrading packages for a while. You can try deleting: This post about another package might have some useful info: icetee/remote-ftp#839 |
apm rebuild from within atom seemed to fix, from the command line it did not fix thanks for the help |
Good stuff! |
I just did a clean install. I right clicked on project -> remote sync -> configure, nothing happens.
I also tried manually create the config file and still noting.
Is this supposed to work on OSX?
Thanks
The text was updated successfully, but these errors were encountered: