At work I regularly edit files that resides on the server. I do it in
one of two ways - either Interarchy using the edit command or mounting
the remote server using ExpanDrive. Both these solutions use sftp (in
my case).

On Sun, Aug 31, 2014 at 1:35 AM, Gregory Shenaut <[email protected]> wrote:
> Would sshfs (in macports) be an option? I used this once in 2009 to do 
> something similar.
>
> Greg Shenaut
>
> On Aug 30, 2014, at 15:50 , Charlie Garrison <[email protected]> wrote:
>
>> Good morning,
>>
>> On 30/08/14 at 2:46 PM -0700, Andrew B <[email protected]> wrote:
>>
>>> * Is it possible to invoke BBEdit to edit a file using a command on a
>>> remote Linux machine?  The bbedit tool seems to do exactly this on the
>>> local OSX machine, but I'm wondering if anyone has magic that could
>>> accomplish the same result remotely.
>>
>> I'm not aware of anything to do this. There have been past attempts (even by 
>> me) but nothing successful. The best I came up with was automating the 
>> process of:
>>
>> - scp localfile osxhost:localfile
>> - ssh osxhost bbedit -wait --resume localfile
>> - scp osxhost:localfile localfile
>>
>> It was too fragile though; it was quite a while ago and I don't recall the 
>> problems.
>>
>> I'd love to hear someone else saying they have a solution for this one. 
>> Would be great if I could set EDITOR on remote machines to point back to 
>> bbedit.
>>
>>> * Can the BBEdit shell workspace be directed to any SSH connection?
>>
>> The worksheet is not a TTY, so you cannot have an ssh *session*. You can 
>> send commands to remote servers via ssh from a worksheet (assumes ssh key 
>> login). I use this method quite a lot to (eg) set permissions for files on 
>> remote server, or restart a running process on remote server, etc. I also 
>> use worksheet to copy files to remote server using rsync; especially handy 
>> for mirroring sites.
>>
>>> * I am assuming that between the open via ftp/sftp, and the mounting of
>>> remote file systems, BBEdit should be able to access and edit the
>>> remote files.  Are there any gotchas here I should be aware of?
>>
>> There may be some gotchas, but none I think you need to be aware of. BBEdit 
>> has quite good handling of files on remote volumes. I sometimes use the 
>> built-in s/ftp tools; I used to use external s/ftp (Interarchy) almost 
>> exclusively; I now use mounted remote volumes with ExpanDrive.
>>
>> [The new version of ExpanDrive has introduced some strange race conditions 
>> with its new local file cache; I've not found the reproducible steps yet. 
>> Anyone else seeing problems with new ExpanDrive 'modifying files since last 
>> save'?]
>>
>> As someone new to BBEdit, you will bring a fresh perspective to editing 
>> files on remote servers. I look forward to hearing what solution(s) you find 
>> work best for you.
>>
>>
>> Charlie
>>
>> --
>>   Charlie Garrison  <[email protected]>
>>   github.com/cngarrison   metacpan.org/author/CNG
>>
>> O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
>> http://www.ietf.org/rfc/rfc1855.txt
>>
>> --
>> This is the BBEdit Talk public discussion group. If you have a feature 
>> request or would like to report a problem, please email
>> "[email protected]" rather than posting to the group.
>> Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
>>
>> --- You received this message because you are subscribed to the Google 
>> Groups "BBEdit Talk" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To post to this group, send email to [email protected].
>

-- 
This is the BBEdit Talk public discussion group. If you have a 
feature request or would like to report a problem, please email
"[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>

--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].

Reply via email to