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

Assumes default search path and download path to be the application path #8581

Closed
cyberduck opened this issue Feb 13, 2015 · 2 comments
Closed
Assignees
Labels
bug cli Command Line Interface fixed
Milestone

Comments

@cyberduck
Copy link
Collaborator

be85312 created the issue

I was testing duck with doing simple uploads and downloads of files, and found that if a path is not specified for a file, i.e. just its name in the current directory is specified, duck will assume that it should look for it, or download it into, the application folder, /opt/duck/app/. This is really unintuitive. I was able to successfully perform operations by specifying the file as a path, in my case simply ~/, worked, but I believe that the default search path should be the directory the user is running duck within. This is as of fc930c4.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We are having issues finding the current working directory.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 6514091.

@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.
Labels
bug cli Command Line Interface fixed
Projects
None yet
Development

No branches or pull requests

2 participants