Cyberduck Mountain Duck CLI

#3883 closed defect (fixed)

Edit With saves files in -Tmp- in incorrect directory names

Reported by: jwagon@gmail.com Owned by: dkocher
Priority: normal Milestone: 3.3
Component: core Version: 3.3b4
Severity: normal Keywords:
Cc: Architecture:
Platform:

Description (last modified by dkocher)

  1. Open an SCP connection with Cyberduck on a server at path /X/Y
  2. Navigate to file test.txt, located at path /X/Y/Z/test.txt
  3. Choose command-K to Edit With...
  4. File opens in default editor.

All of that works great, but then if I look for the downloaded copy of test.txt in the Finder, it's located at

-Tmp-
  /X/Y/Z
    test.txt

whereas the correct directory structure used to be set up in -Tmp- with this download, like this:

-Tmp-
  X
    Y
      Z
        test.txt

This eventually becomes a problem when you later decide you want to open a file at /X/Y/ABC/another_file.txt, because then your -Tmp- directory will look like

-Tmp-
  /X/Y/Z
    test.txt
  /X/Y/ABC
    another_file.txt

instead of what you'd expect, which would be:

-Tmp-
  X
    Y
      Z
        test.txt
      ABC
        another_file.txt

Change History (3)

comment:1 Changed on Nov 4, 2009 at 12:15:19 PM by jwagon@gmail.com

I suppose this isn't a big deal for many users, but for people who use TextMate with Cyberduck it is. This is because we like to open up Cyberduck to the root directory of a project on a remote server and be able to download files anywhere in that project directory tree, and then just open the local directory corresponding to the project root (which was downloaded to -Tmp- via Cyberduck) in TextMate as a "Project", providing us with a convenient and fast synchronization method for just the subset of files that we download.

Again, this is how Cyberduck used to work (I think my last version was 3.2 on Leopard). But now with this strange new (3.3bX on Snow Leopard) behavior of naming directories with remote pathnames and ignoring a document's original location within the project, this is impractical with non-trivial projects.

Cyberduck's synchronize feature is the logical option, but this is also impractical for any sizable project, even over a relatively fast connection; it just takes too long.

Can we restore the original download behavior?

comment:2 Changed on Nov 4, 2009 at 12:24:57 PM by dkocher

  • Description modified (diff)
  • Milestone set to 3.3
  • Status changed from new to assigned

comment:3 Changed on Nov 5, 2009 at 3:36:42 PM by dkocher

  • Resolution set to fixed
  • Status changed from assigned to closed

In r5529.

Note: See TracTickets for help on using tickets.