I misunderstood your previous post -- your solution is better than I thought at first. I will give it a go to see how it works in practice. I agree that using an existing protocol & daemon is preferable (less work, if nothing else). Usually I find that script-based solutions are fragile, and your comment to that effect made me suspicious. :)
On Sunday, August 31, 2014 11:30:33 PM UTC-7, Charlie Garrison wrote: > > Good afternoon, > > On 31/08/14 at 6:38 PM -0700, Andrew B > <[email protected] <javascript:>> wrote: > > >Too ambitious? > > Don't know, but not sure how that is much better than using SSH > as the daemon. All the communication can already be done with > SSH, so why introduce another protocol into the mix? > > The IP address of the BBEdit machine should be easy enough to > get from the current login session, and then just set an > environment variable that the script uses. > > Pretty much all the limitations with script I attached earlier, > can be solved with additional coding to harden the script. Even > the requirement for ExpanDrive could be replaced with `scp` commands. > > The script does require 'remote login' to be enabled on the > BBEdit machine, but I don't see that as any more of a burden > than a separate daemon for this purpose. > > Charlie > > -- > Charlie Garrison <[email protected] <javascript:>> > 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].
