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

Execute Send Command in current working directory of browser #6021

Closed
cyberduck opened this issue Jun 22, 2011 · 1 comment
Closed

Execute Send Command in current working directory of browser #6021

cyberduck opened this issue Jun 22, 2011 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

bde6931 created the issue

When sending a command to the remote server, such as "wget", execute the results in the same directory the user is currently browsing in the Cyberduck window.

This way the file downloaded to the remote server (still using the "wget" example) will be where the user expects to see it. Currently commands default to executing on the home directory of the logged in server user, requiring us to either find the file and mv it to the desired directory, or to type (using a drupal installation as the example):

wget ~/public_html/sites/all/modules/date-7.x-2.0-alpha3.tar.gz http://ftp.drupal.org/files/projects/date-7.x-2.0-alpha3.tar.gz

... even if we're currently looking at the sites/all/modules directory.

With this enhancement the command would become simply:

wget http://ftp.drupal.org/files/projects/date-7.x-2.0-alpha3.tar.gz

This is a matter of convenience and end-user expectation. However, considering the destructive power of some CLI commands such as "rm", this enhancement could conceivably also prevent serious unexpected results.

@cyberduck
Copy link
Collaborator Author

bde6931 commented

thinking more on this request this morning, considering that many folks are likely used to the current behavior, rather than change the default behavior perhaps provide a "execute in directory being browsed" checkbox to the Send Command pane.

@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

1 participant