Skip to content
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

All documents opened twice when editing #2162

Closed
cyberduck opened this issue Jun 2, 2008 · 10 comments
Closed

All documents opened twice when editing #2162

cyberduck opened this issue Jun 2, 2008 · 10 comments
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Jun 2, 2008

9e7d5f1 created the issue

Each time I double-click on Cyberduck 3 (build 3999) to open a file in Smultron, it opens two copies of the file.

Thank you!


Attachments

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jun 4, 2008

@dkocher commented

#2169 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jun 30, 2008

@dkocher commented

#2206 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jun 30, 2008

@dkocher commented

Cannot replicate this. Please try the latest nightly build from (http://update.cyberduck.ch/nightly).

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jun 30, 2008

9e7d5f1 commented

I have confirmed that this problem still exists with build 4022. With some files, the MacOS also opens up one copy of the file in another editor (e.g., .txt files in Textedit). I was not able to use builds 4048 or 4050, since Cyberduck would not always successfully navigate from one directory to another.

Richard

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jun 30, 2008

@dkocher commented

Build 4059 should work. Can you try with this and also rebuild the launch services database using

/System/Library/Frameworks/ApplicationServices.framework/\
Frameworks/LaunchServices.framework/Support/lsregister \
-kill -r -domain local -domain system -domain user

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jun 30, 2008

9e7d5f1 commented

Problem recurs with Build 4059.

The command you sent returned the following result:

kassissieh-mac:~ kassissiehr$ /System/Library/Frameworks/ApplicationServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user
-bash: /System/Library/Frameworks/ApplicationServices.framework/Frameworks/LaunchServices.framework/Support/lsregister: No such file or directory

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jul 2, 2008

@dkocher commented

Can you please let me know if this only happens Smultron or other editors as well?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jul 8, 2008

9e7d5f1 commented

I think I have found the solution.

In Cyberduck -> Preferences -> General -> Downloads, uncheck "open downloaded files with default application." I still have Smultron selected as Cyberduck's default text editor in Cyberduck -> Preferences -> External editor. Now, Smultron only opens one copy of each script. In previous versions of Cyberduck, this didn't happen. Now, it appears that Cyberduck opens one copy of the downloaded file in the default application and another in the external editor. In cases where the external editor is also the default application for that file type (in my case, .pl and .php), this results in two copies open in Smultron. In cases where another application is the default (e.g., .txt), then one copy opens in that application.

For me, it isn't a problem to disable the automatic opening of downloaded files in the default application, because I only use Cyberduck for coding projects. For someone using Cyberduck for both generic file transfers and programming, I imagine that this could become a feature request.

Let me know if this is indeed the final solution. Many thanks for your attention to this case.

Richard

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jul 10, 2008

@dkocher commented

Thanks for your additional comment. It is now clear to me what the problem is.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jul 11, 2008

@dkocher commented

In 2abb5a0.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants