[Cyberduck-trac] [Cyberduck] #9727: Remote File-Path Obfuscated in Text Editor

Cyberduck trac at trac.cyberduck.io
Thu Oct 6 16:40:44 UTC 2016


#9727: Remote File-Path Obfuscated in Text Editor
--------------------------------------------------+----------------------
 Reporter:  moghilemear                           |         Owner:
     Type:  defect                                |        Status:  new
 Priority:  normal                                |     Milestone:
Component:  core                                  |       Version:  5.1
 Severity:  normal                                |    Resolution:
 Keywords:  Editor filepath too long for display  |  Architecture:  Intel
 Platform:                                        |
--------------------------------------------------+----------------------
Description changed by moghilemear:

Old description:

> Issue: file path displayed by text editor is obfuscated
> Cyberduck 5.1.3, OSX 10.12, TextWrangler 5.5.2
>
> Class: it is not clear whether this is a feature, enhancement, or defect
> class of issue.  Also, this is associated with a collaboration between
> Cyberduck & Textwrangler/BBedit apps.
>
> TextWrangler is a standard text editor for OSX, and is configured as my
> Cyberduck editor.  When editing a remote file (selected via Cyberduck
> interface), TextWrangler displays the the *local - temporary* filepath,
> (not the remote filepath).
>
> This may or may not be the intended design of Cyberduck (i.e. show the
> local filepath) the problem is that the local path is extremely long and
> therefore useless when attempting to identify the originating location
> (i.e. remote dir path) of the file.
>
> I reported this to TextWrangler.  Upon investigation of the matter the
> tech team directed me to report this to Cyberduck as well (citing that it
> is a collaboration issue).
>
> TextWrangler provided me with a more technical description:
> ''"BBEdit and TextWrangler rely on CyberDuck passing certain information
> in the 'odoc' event, indicating the file's origin. It looks as though
> when CyberDuck changed over to use file monitoring to detect when the
> file is saved, it stopped doing this, so that BBEdit and TextWrangler
> have no way to know where the file came from (and thus no information
> available to display the remote path)."''
>
> If this is not a defect, then I would like to request that there be a
> Cyberduck Config parameter, to allow the user to control whether the
> local or remote file-path is displayed.
>
> Here is an example of just the tmp dir part of the displayed filepath
> "/private/var/folders/gh/9zlxkcdd68b6kgrtw85nx4s80000gn/T/daeac1d1-cb66-43d1
> -b4aa-33258716b313/<remote filepath goes here>"

New description:

 Issue: file path displayed by text editor is obfuscated
 Cyberduck 5.1.3, OSX 10.12, TextWrangler 5.5.2, Remote: Linux CentOS 7

 Class: it is not clear whether this is a feature, enhancement, or defect
 class of issue.  Also, this is associated with a collaboration between
 Cyberduck & Textwrangler/BBedit apps.

 TextWrangler is a standard text editor for OSX, and is configured as my
 Cyberduck editor.  When editing a remote file (selected via Cyberduck
 interface), TextWrangler displays the the *local - temporary* filepath,
 (not the remote filepath).

 This may or may not be the intended design of Cyberduck (i.e. show the
 local filepath) the problem is that the local path is extremely long and
 therefore useless when attempting to identify the originating location
 (i.e. remote dir path) of the file.

 I reported this to TextWrangler.  Upon investigation of the matter the
 tech team directed me to report this to Cyberduck as well (citing that it
 is a collaboration issue).

 TextWrangler provided me with a more technical description:
 ''"BBEdit and TextWrangler rely on CyberDuck passing certain information
 in the 'odoc' event, indicating the file's origin. It looks as though when
 CyberDuck changed over to use file monitoring to detect when the file is
 saved, it stopped doing this, so that BBEdit and TextWrangler have no way
 to know where the file came from (and thus no information available to
 display the remote path)."''

 If this is not a defect, then I would like to request that there be a
 Cyberduck Config parameter, to allow the user to control whether the local
 or remote file-path is displayed.

 Here is an example of just the tmp dir part of the displayed filepath
 "/private/var/folders/gh/9zlxkcdd68b6kgrtw85nx4s80000gn/T/daeac1d1-cb66-43d1
 -b4aa-33258716b313/<remote filepath goes here>"

--

--
Ticket URL: <https://trac.cyberduck.io/ticket/9727#comment:6>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows


More information about the Cyberduck-trac mailing list