8000 DO NOT USE THIS remote edit PACKAGE WITH ATOM · Issue #246 · sveale/remote-edit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

DO NOT USE THIS remote edit PACKAGE WITH ATOM #246

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

Open
connormcmk opened this issue Sep 5, 2018 · 0 comments
Open

DO NOT USE THIS remote edit PACKAGE WITH ATOM #246

connormcmk opened this issue Sep 5, 2018 · 0 comments

Comments

@connormcmk
Copy link

For those of you looking for a remote edit tool, this is not the tool to use. Don't get me wrong, it performs the basic needs of a remote edit package, but it has the enormous downside of largely being abandoned.

I highly recommend using a different remote edit tool like:
remote-ftp
or
ftp-remote-edit

Not only are these more convenient, but they are also being maintained.

remote-ftp downloads the files to your local machine and then upon saving uploads them on the remote machine. This will allow you to use all the functionality of atom (like token definition searches) as if you were working on the code locally (because you are).

ftp-remote-edit allows you to edit the remote files without having to download the files. This is convenient if you prefer to not build up a bunch of files on your local machine, or if you are concerned about the data costs of transferring whole repositories (packages) back and forth. I haven't used this package much, but it seems to be maintained as well, so I'm adding it to the list.

No shade for the original creator, just want to help other people avoid the productivity sink this caused me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant
0