sveale / remote-edit

remote-edit
MIT License
146 stars 55 forks source link

Files are not displayed after successfully reading from remote server #143

Closed IntegersOfK closed 8 years ago

IntegersOfK commented 8 years ago

As of today, when I open a file from a remote server (sftp), the green alert says that the file was read successfully (as expected). Normally Atom would then display a new tab with the file, but no new tab opens and my workspace remains blank. When I list the downloaded files with "Show open files", they're all there. Again when I click on one, Atom does not actually open or display the file in the editor window. No errors are displayed and there's nothing to suggest a problem with the fileserver.

I am using MacOS 10.10.5. I can see when I download a file that the json config file for remote edit is updated with the file's server and cache information, and the files are downloaded locally into a subdirectory in my /private folder. The files simply don't open in the editor window.

asimshamim2015 commented 8 years ago

I am also experiencing this issue! It will read the remote file, however it won't load.

rekikn commented 8 years ago

Im can't see the files too. Clean reinstall of Atom don't fix error :/

westonkd commented 8 years ago

Same

boscolau commented 8 years ago

Issue occurs after upgraded to Atom 1.2.0 Reinstalled Atom 1.1 the problem was gone, but Atom would auto update to 1.2.0. Cannot disable autoupdate, so this is still a problem

asimshamim2015 commented 8 years ago

I've temporarily fixed this issue.

Hope this helps

adriangordon1231 commented 8 years ago

I am having this issue as well.

fburleigh commented 8 years ago

Same in Atom 1.3 beta:

Uncaught (in promise) Error: Must pass a config parameter when constructing TextEditors

nobutsta commented 8 years ago

Also not work on Atom 1.2.3, uninstalled already.

rabgc commented 8 years ago

I experience this issue also.

basilfawlty commented 8 years ago

Same issue here. Is this going to be fixed?

drq883 commented 8 years ago

There is a pull request for a patch to fix this by user tk3369

https://github.com/sveale/remote-edit/pull/152

sveale commented 8 years ago

Published mike's PR #146 that should fix the issue., see remote-edit@v1.8.23.

drq883 commented 8 years ago

Thanks. I've missed it.

On Dec 5, 2015, at 8:26 AM, Sverre Aleksandersen notifications@github.com wrote:

Published mike's PR #146 that should fix the issue., see remote-edit@v1.8.23.

— Reply to this email directly or view it on GitHub.

drq883 commented 8 years ago

How long does it normally take for Atom Available Updates to see newly built packages?

sveale commented 8 years ago

Usually instant. Do you have the newest atom version?

---- David Quattlebaum skrev ----

How long does it normally take for Atom Available Updates to see newly built packages?

— Reply to this email directly or view it on GitHub.

drq883 commented 8 years ago

1.2.1

It’s downloading an update now (over my parent’s SLOW network).

sveale commented 8 years ago

That's probably the reason. The fix is only for 1.2.3+ I think.

---- David Quattlebaum skrev ----

1.2.1

It’s downloading an update now (over my parent’s SLOW network).

— Reply to this email directly or view it on GitHub.

drq883 commented 8 years ago

Updated Atom to 1.2.4, remote-edit to 1.8.23. I'm now back in business.

Thanks @sveale and @mike-kfed for fixing this.

IntegersOfK commented 8 years ago

Confirmed fixed! I am happy we got to the bottom of this, thanks guys.