External editor opens extra windows

The Cyberduck forums have moved to Google Groups, this forum is read only.
Locked
JonasOnline
Harmless
Posts: 3
Joined: Tue Jan 23, 2007 3:54 am

External editor opens extra windows

Post by JonasOnline »

I have a text editor, BBEdit (version 7.1.4), set as the external editor for CyberDuck (version 2.7.2), running in Mac OS X (version 10.3.9).

This works, but every time it opens a file from CyberDuck, BBEdit opens *two* windows: the actual file in front, plus a big blank "Untitled" BBEdit window behind it. This happens regardless of whether I open the file within CyberDuck by double-clicking it, or right-clicking and choosing "Edit with BBEdit", or use the Command-J command, or click the BBEdit icon in CyberDuck's title bar.

This isn't a killer, of course, but it is quite annoying to have to close a superfluous text window every time I edit a file from CyberDuck. Any idea what's causing this, and whether there's anything I can do to stop the extra blank window from opening each time?
iMoo
Harmless
Posts: 4
Joined: Mon Jan 22, 2007 1:39 pm

Post by iMoo »

Just a wild guess, since I haven't worked with BBEdit for a long time. Doesn't BBEdit open a new window by default on its own when you start the program? That way it loads its new window, and the second window for the file you selected.

Maybe there's an option in the BBEdit preferences to start without opening a new document.

Good luck!
And by the way, Adium is so great!
JonasOnline
Harmless
Posts: 3
Joined: Tue Jan 23, 2007 3:54 am

Post by JonasOnline »

iMoo wrote:Doesn't BBEdit open a new window by default on its own when you start the program?
Yes, that was the answer.

Actually, this implies a subtle problem in CyberDuck, I think. I normally keep BBEdit running; it wasn't "launching" each time CyberDuck told it to open a file. Typically (at least with other FTP apps I've used) BBEdit sees that as a simple 'open this file' request, not as though it were launching for the first time. I suspect CyberDuck is sending it the wrong Apple Event, or something like that.

Thanks much for your help.
Locked