[tahoe-lafs-trac-stream] [tahoe-lafs] #2027: Inconsistent 'tahoe cp' Behavior

[tahoe-lafs]

#2027: Inconsistent 'tahoe cp' Behavior
-------------------------------+------------------------
 Reporter:  markberger         |          Owner:
     Type:  defect             |         Status:  new
 Priority:  normal             |      Milestone:  1.11.0
Component:  code-frontend-cli  |        Version:  1.10.0
 Keywords:                     |  Launchpad Bug:
-------------------------------+------------------------
 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.jgp
 ~/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.jgp ~}}} succeeds along with {{{tahoe cp
 tahoe:test/test.jgp ~/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.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2027>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage