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

Editor Files Moved To Trash #3264

Closed
cyberduck opened this issue Jun 23, 2009 · 1 comment
Closed

Editor Files Moved To Trash #3264

cyberduck opened this issue Jun 23, 2009 · 1 comment
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

e729dee created the issue

By default behavior, CyberDuck moves files from a temporary folder to the Trash whenever an Editor is closed (when the editor is used to edit a file that resides on the server). This is a fine feature, but it can get annoying on a day to day basis where I edit a lot of files on my server using CyberDuck and my editor, and then have a collection of files sitting in my trash when done.
What I would like to propose is an option in the Preferences to permanently delete those files, instead of moving them to the trash, upon successful upload to the server. Thus, the workflow would go as such:

  • Edit a file from the server via CyberDuck
  • Save the file (the file gets uploaded back to the server, via CyberDuck
  • Close the editor.
  • CyberDuck sees the file hasn't changed since the last upload, so it has to decide what to do with the temporary file.
  • If the preferences say move to Trash, then move the file to Trash.
  • If the preferences say delete the file, then permanently delete the file.

Could this be added as a feature? I am severely OCD about keeping my Trash empty, and I hate it getting unecessarily cluttered. Thanks!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

As of 4866, set the property editor.file.trash to false using

defaults write ch.sudo.cyberduck editor.file.trash false

This will cause the edited file to be deleted instantly.

@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