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

New filenames for tmp files for editing are confusing #1101

Closed
cyberduck opened this issue Apr 18, 2007 · 2 comments
Closed

New filenames for tmp files for editing are confusing #1101

cyberduck opened this issue Apr 18, 2007 · 2 comments
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

cf7497a created the issue

Since this new build, when downloading files to a temporary directory for opening them up in a browser, Cyberduck saves the entire remote path in the filename, converting slashes to underscores. I guess that this was done to prevent name conflicts among files that have the same name but are in different directories, which, in the previous builds, were being downloaded as "filename-N.extension". However, this is quite confusing - if your remote path is long, all you see in the file list in most editors (I use Smultron) is the first part of the temporary path, which is the same for all the files!

It would be much better to solve the potential conflict by recreating a directory tree inside the temporary directory (one dir per server and then recreating the remote path from root) and putting each file in the correct directory without changing the name.

At least, that what I'd prefer - I'm thinking about reverting back to the last build because this new one is really a problem. If other people prefer the new approach, perhaps it could be a configuration setting?

Thanks a lot for your work,

@cyberduck
Copy link
Collaborator Author

cf7497a commented

(sorry, I meant that what you see of the filename is only the first part of the remote path converted in the temporary filename... anyway, something from which you can't tell the different files)

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Fixed in cd5f944.

@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