At 2:44 PM -0600 8/15/07, Doug McNutt wrote:
At 15:06 -0500 8/15/07, Shelda Eggers wrote:
I know I risk sounding like a broken record here, but the "new and improved" BBEdit FTP browser is about to send me 'round the bend!

Anybody who can respond to this? Anybody found a workaround?

Personally I use a BBEdit worksheet where I store curl or scp commands for the files I'm using. I just make the worksheet frontmost and pick the right line to execute - down or up. That either gives me a local file to work on or replaces an edited file on a server. Either way I not only get the edited file where I want it but I have backups during the process.

Once you get one curl or scp pair set up it's quite easy to copy those and make new ones as you discover other files you want to work with. Curl handles passwords in a $HOME/.netrc file and scp will work with certificates in totally transparent fashion.

A line calling the bbedit tool is easily added to open a downloaded file automatically.

Why wouldn't you open the files directly with the bbedit tool? I use things like "bbedit sftp://[EMAIL PROTECTED]//etc/passwd sftp://[EMAIL PROTECTED]//etc/shadow" all the time; I see no reason to manage the local copies manually. Open Recent also works with such files.

        You could do that from a BBEdit worksheet if you wanted.

I've just discovered that Open Selection doesn't work against "sftp://www//etc/passwd"; (no quotes); I filed a bug.


                                                Chris
--
Chris Pepper:                <http://www.reppep.com/~pepper/>
                             <http://www.extrapepperoni.com/>
The Rockefeller University:  <http://www.rockefeller.edu/>

--
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
If so, please send mail to <[EMAIL PROTECTED]>, not to the list.
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>
To unsubscribe, send mail to:  <[EMAIL PROTECTED]>

Reply via email to