-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
Closing opened file in editor won't always allow you to reopen #7248
Comments
I am experiencing this behaviour as well on OS X 10.8.3, after opening files and then subsequently closing them some time later, attempting to open an editor session again from Cyberduck fails even if I select a different editor. Cyberduck shows that it is downloading the file, but then the editor does not open. |
Same here. OS X 10.8.3. |
Can you find any related output in the |
Nothing interesting there under 'All Messages' nor system.log. I can reproduce the issue reliably by performing the following steps:
Cyberduck will download the file, but not open the editor again. |
Also happening here on OS X 10.8.3 as of Cyberduck version 4.3.1 build 11010, although I'm unsure what exact circumstances cause the problem...firewing1's steps didn't manually ignite the issue for me. It almost seems random. |
I have the same issue on MAC OS. There is the same issue with every text editor. To reproduce the issue:
|
Replying to [comment:10 josco]:
Thanks for commenting. Can you replicate this with the latest snapshot build available? |
Sometimes when you open a file in editor through ftp, and close out of it, it will not allow you to reopen the file. You got to close out of cyberduck and reopen it. This is on Windows 8 and 7
The text was updated successfully, but these errors were encountered: