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
Preference to suppress additional attribute columns when copying filename #10710
Comments
Hi, I certainly understand the reasons behind this feature, but isn't there a way to by pass it with a combination of keys? I work all day long on servers and I press the delete button on my terminal countless of times due to this feature. The way would be to download an older version of cyberduck, but I am not comfortable not having the latest updates. What do you think? |
My comment on this is in the context of #10735 having been closed, and this issue being converted to a feature-request. (is it a bug or a feature issue) My argument is that this is a bug and not a feature, and should be addressed as such.
While I agree that the "Preferences" option might be a good compromise, there is much stronger evidence that the default behavior should be OSX standard (i.e. full path). The enhanced clipboard data-structure should be a preferences setting change. |
My comment on this is in the context of #10735 having been closed, and this issue being converted to a feature-request. (is it a bug or a feature issue) My argument is that this is a bug and not a feature, and should be addressed as such.
While I agree that the "Preferences" option might be a good compromise, there is much stronger evidence that the default behavior should be OSX standard (i.e. full path). The enhanced clipboard data-structure should be a preferences setting change. |
Hi,
whenever I copy the path or a file directly from Cyberduck interface, I get extra numbers at the end of the folder/file path. This first happened almost a year back. I am using a Mac OS 10.14.5.
Example:
/mypath/myfile.txt,6057,1558628255000
The text was updated successfully, but these errors were encountered: