Brackets Won't Open Files When Using Cyberduck's "Edit" Feature

[dartanian300]

I'm running Windows 7 Home Premium 64-bit with Brackets v1.1.

When using Cyberduck's "edit" feature that automatically downloads the file, opens it in your editor, and reuploads it on save, Brackets gives me an error that says:

"Error Opening File
An error occurred when trying to open the following files:
- The file/directory could not be found."

I've tried this feature with other editors and it works just fine. However, if Brackets is closed and I try to use this feature it works fine. It's as if Brackets is trying to open the file before it's finished downloading.

[JeffryBooher]

Also happens on Mac.

[JeffryBooher]

Brackets shell currently takes all of file names passed to it on the command line and makes them available to brackets core to open after its UI has bootstrapped. It may be that cyberduck isn't passing them in a way that we cannot not parsing correctly so it's a matter of having someone install cyberduck and use the edit feature in conjunction with a debug version of brackets to see what the command line looks like so we can parse it correctly then test on both Windows and Mac

[peterflynn]

Note that is is only expected to work on Windows for now. For other platforms, see these feature requests: Open File/Folder from Command Line on Mac, Open File/Folder from Command Line on Linux.

For Windows as Jeff said it should work. To find out why not, we need to see how Cyberduck is passing the files on the command line. @dartanian300 can you do this for us?

1. Open Task Manager and go to the Processes tab
2. Using View > Select Columns, add Command Line to the list of columns
3. Use the "edit" feature in Cyberduck to try opening the file. Leave Brackets open with the error message showing.
4. In Task Manager, look for the two Brackets.exe processes. In the Command Line column, one will say --type=renderer. What does the other Brackets.exe Command Line column say?