Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leopard: Edit in BBEdit not working #1334

Closed
cyberduck opened this issue Nov 12, 2007 · 8 comments
Closed

Leopard: Edit in BBEdit not working #1334

cyberduck opened this issue Nov 12, 2007 · 8 comments

Comments

@cyberduck
Copy link
Collaborator

88674df created the issue

Cyberduck 2.8 (3257)
BBEdit 8.7.1 (240)
Mac OS X 10.5 (9A581)

The 'EDIT' button in Cyberduck will still open the selected file in BBEdit. But upon save in BBEdit the file is not uploaded back any more.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

See #1244.

@cyberduck
Copy link
Collaborator Author

d160e32 commented

hallo david,
bei mir hat's dasselbe problem: cyberduck (3.2.1 auf OS X 10.4.11) sendet zu bearbeitende dateien zwar (nach einiger wartezeit) an bbedit, das speichern in BBE wird aber nicht von cyberduck uebernommen ... woran kann das liegen? ich hab das problem nur an einem rechner, ein anderer mit aehnlicher konfiguration hat keine schwierigkeiten ,~(
ansonsten: arbeite grade zum ersten mal ernsthaft mit cyberduck, tolles programm, merci bien!!
-martin

@cyberduck
Copy link
Collaborator Author

35d72d1 commented

Having the same problem with TextWrangler on Snow Leopard.
(Sorry, I don't understand German :) )

Was working well with Cyberduck 3.5 But since upgrading to 3.5.1 I get the following result:

  • In Cyberduck, open a .php file for editing in TextWrangler (The good point is that TextWrangler shows the path to the file at the top of the window, and updates it dynamically when the file moves.)
  • In TextWrangler I can see that the path to the file is something like: /private/var/folder/.../myfile.php (ie. it is in a temporary folder)
  • After 1 second the path changes to ~/.Trash/myfile.php

I think that Cyberduck believes that I am done with editing the file and thus trashes it.

Cyberduck 3.5.1 (6117), TextWrangler 3.1 (2640), Snow Leopard 10.6.3 (10D573)

JL

@cyberduck
Copy link
Collaborator Author

35d72d1 commented

I confirm that the problem does not appear with Cyberduck 3.5 (6066)
I just downloaded this version to test it.

(Sorry if I messed the properties of this ticket. It was not intended. I am resetting them back to what they were. You can change the properties to whatever you want :) )

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I cannot replicate the issue here. Can you find any related output in the system.log (/Applications/Utilities/Console.app)?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Duplicate for #4440.

@cyberduck
Copy link
Collaborator Author

35d72d1 commented

Ok, i think I found something interesting. I cannot reproduce this exact issue, but I found something that may explain the strange behavior, despite I dont know how.

In short: editing 2 files with same path same name on different websites will overwrite each other.

Step to reproduce:

  • have 2 navigator windows opened and connected to 2 different websites.
  • have 2 files with the same name and same path on both sites
  • open for editing each one in turn. (and reopen them again as many times as you want)
  • see in your editor that it is the same file that locally represents the 2 different remote files from the 2 websites.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:7 jlgrall]:

Ok, i think I found something interesting. I cannot reproduce this exact issue, but I found something that may explain the strange behavior, despite I dont know how.

In short: editing 2 files with same path same name on different websites will overwrite each other.

Step to reproduce:

  • have 2 navigator windows opened and connected to 2 different websites.
  • have 2 files with the same name and same path on both sites
  • open for editing each one in turn. (and reopen them again as many times as you want)
  • see in your editor that it is the same file that locally represents the 2 different remote files from the 2 websites.

This has been fixed. Refer to #4989.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants