search

sveale / remote-edit

remote-edit
MIT License
146 stars 55 forks source link

remote-edit is unresponsive #186

Open bladorf opened 8 years ago

bladorf commented 8 years ago

I've been using this package (thanks!) for the last few months, and this morning pressing cmd+ctrl+B didn't open up the browser. I tried clicking through the menus but clicking that option did nothing as well.

It turns out none of the remote-edit options perform any sort of action, and restarting my computer, restarting atom, uninstalling remote-edit and reinstalling it, and uninstalling atom and reinstalling it all didn't fix the problem.

edit: I also tried removing the package from ~/.atom/.apm/.remote-edit/ and re-installing, but the behavior (nothing happens when I select any of the options) is the same.

Any ideas on what to do from here?

screen shot 2016-07-18 at 10 45 47 am

bladorf commented 8 years ago

This issue was fixed by 'rebuilding packages' which came up as a bug option at the bottom of atom.

dmase44 commented 8 years ago

I'm having the same issue. I have been using the atom beta versions. It worked great til beta 1.9.0. which will not load remote-edit. I installed the stable 1.8.0 over it & it worked fine til I shut atom down. On restart I get the same error message as before: Cannot find module 'C:\Users\Gonzo\AppData\Local\atom\app-1.9.0\resources\app.asar\src\display-buffer'. I removed every instance of atom I could find. Reinstalled stable 1.8.0 & same issue til I reinstall 1.8.0 over it & it works fine til I shut it down. the error states: The error was thrown from the remote-edit package. This issue has already been reported! It appears it hasn't been resolved as it's been this way for quite awhile. Any ideas?

Nollikino commented 8 years ago

@dmase44 The problem the OP was talking about is not the same problem that you're experiencing.

There are three other issues open which are more "apt" at describing the problem with the "missing" module "display-buffer". You can find them at #188, #189 and #190.

There is also a pull request that is set to resolve this problem. You can find it at #187. If you want to resolve the problem before the pull request is mainlined into the original fork, then you can implement the changes of the code in the pull request manually. Otherwise, your only other solution is downgrade atom and remove auto-update.