Opened at 2013-07-17T14:45:14Z
Last modified at 2015-02-05T02:10:04Z
#2027 closed defect
Inconsistent 'tahoe cp' Behavior — at Version 1
| Reported by: | markberger | Owned by: | daira |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.10.1 |
| Component: | code-frontend-cli | Version: | 1.10.0 |
| Keywords: | usability error cli tahoe-cp review-needed | Cc: | |
| Launchpad Bug: |
Description (last modified by daira)
When copying a file from the top level of a directory node using the CLI, tahoe requires a file name to be specified.
Ex: tahoe cp tahoe:test.jpg ~ fails while tahoe cp tahoe:test.jpp ~/test.jpg succeeds.
However, when a file is copied from a subdirectory to the local disk without a specified file name, the download will succeed.
Ex: tahoe cp tahoe:test/test.jpg ~ succeeds along with tahoe cp tahoe:test/test.jpg ~/test.jpg.
The CLI's behavior should be consistent. Either require users to specify a file name for all cp actions or allow users to copy files from the top level of a directory to a local directory without specifying a file name.
Change History (1)
comment:1 Changed at 2013-07-17T16:15:15Z by daira
- Description modified (diff)
- Keywords usability error cli tahoe-cp easy added
- Owner set to daira
- Status changed from new to assigned
Note: See
TracTickets for help on using
tickets.
