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

Edit in Textwrangler: new useless empty file opened too #6578

Closed
cyberduck opened this issue Mar 8, 2012 · 4 comments
Closed

Edit in Textwrangler: new useless empty file opened too #6578

cyberduck opened this issue Mar 8, 2012 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 8, 2012

7b407ac created the issue

  • Start Textwrangler, close all windows OR close all windows and then exit from TW (in case TW is set to reopen windows from last time)
  • in Cyberduck give the command to edit a file in TW
  • in TW now I see an "untitled file" and the file I wanted to edit

Expected: only the file I wanted to edit.

How to avoid: having a file already open in TW does not present the problem of the unwanted empty files.

When I give the "edit file.txt" command in a bash prompt TW correctly opens only the file I provided, it does not open an empty one too.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 16, 2012

@dkocher commented

This is an issue that has to be fixed in TextWrangler.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 19, 2012

7b407ac commented

Hello,
I contacted BareBones in order to ask them to solve the issue, this is the answer:

I believe this is happening because Cyberduck tells the system to activate TextWrangler before sending it the event to open the document. When you have TextWrangler set to "New Text Document" at startup (which also affects its activation behavior), it will make a new window if no documents are open when it's activated. You can set this to "Do nothing" to work around the problem for now.
On the Cyberduck side, if it can be changed to send the Open Document event to TextWrangler before asking the system to make it the active application, this should solve the problem, as well.

It seems that the issue is is caused by both my TextWrangler settings (that however make sense in most cases) and by a small issue in Cyberduck. Could you please try to correct it, as suggested by Barebones' developers?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 31, 2013

W Breuer commented

In my case:

  • Textwrangler (4.0.1 from appstore) opens with a new file, but without the file I want to edit.
  • Cyberduck (4.2.1 from download) 'halts' for moments with the message it is calculating the MD5 hash.

Spindump available on request.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 8, 2013

@dkocher commented

I cannot replicate this in the latest snapshot build available. Please reopen if this is still an issue for you.

Loading

@cyberduck cyberduck closed this Apr 8, 2013
@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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant