Your best friend for file transfer.Fetch
Fetch 4.0.1 bug: interaction with BBEdit (2 posts)
- Started 13 years ago by dsmcl
- Latest reply 13 years ago from Jim Matthews
System: OS X 10.1.3
One of my favorite features of Fetch 4 is "Command-J" -- edit a file in BBEdit. However on multiple OS X systems, including two with clean installs, my Fetch configuration "loses" the location of BBEdit.
When I try to command-j a text file in the Fetch file listing, I am presented with the following error message:
>> The text editing application (BBEdit) could not be found.
Up until this morning, I was able to correct this error by simply deleting my Fetch 4.0.1 folder and copying a fresh copy from my archive volume. Following this, Fetch would find BBEdit for a while. Eventually (at least once a day), however, it would lose BBEdit again and force me to recopy. Now, however, recopying no longer works and my command-j functionality is absent.
In Fetch's preferences, I have it set to use BBEdit for editing files, but I can't find an option to specify BBEdit's path. I would think that if one were able to specify the path, Fetch would never lose BBEdit's location.
Has anyone else experienced this problem?
Jim Matthews Administrator
This is a known problem, which will be fixed in Fetch 4.0.2. Another workaround is to rebuild the classic desktop; you can do that in the Classic pane in System Preferences.
- Page 1
This topic has been closed.