-
Notifications
You must be signed in to change notification settings - Fork 54
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
Impossible to scroll down after update to Atom 1.19.0 #228
Comments
Same here. I had noticed that issue with Atom.Beta and tried the stable version but same issue. |
Same |
I feel your pain too, brother.. |
ssh to the machine and use vi. that's what I did before remote-edit came along. |
I found this : https://github.com/libfuse/sshfs |
I just installed ftp-remote-edit. I uses sftp (if you restart atom you can enter your ssh key path). It also encrypts traffic to remote with a master key you provide on install. It's a little different but seems to meet the need. It is activated by Ctrl-space and shows a directory listing on the right hand side for you to choose your file. There hasn't been any commit activity to this package since February and not no issues have been closed for quite a while. |
@thbtmntgn I'm also experiencing the same thing. I think we may all need to finally abandon this package for something still maintained. 😭 |
@drq883 I had this error happen with ftp-remote-edit. You haven't had any problems? |
Same issue for me as well. remote file not scrolling down. |
Late to the party, but this is still broken for 1.19.3. Only possibly new detail to report is that if you vertically split the window, and get a view of the bottom of a file, one cannot scroll up. In any event, the initial view is frozen vis a vis scrolling and cannot find a way to shift it up or down. |
A PR has been submitted which fixes this issue: #229 |
I can second that PR #229 works. (Atom 1.19.7 x64) |
Hello,
I just update to Atom 1.19.0 and I can't scroll down within a remote file anymore.
Am I the only one with this problem ?
Best,
Thibaut
The text was updated successfully, but these errors were encountered: