9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "marius a. eriksen" <marius@monkey.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Using Acme Remotely
Date: Fri, 26 Oct 2012 10:51:58 -0700	[thread overview]
Message-ID: <CAPtk8tv91GKtMhbqG0X7h2Vke9QEHzuiTnOBni1QSwBtywOwbw@mail.gmail.com> (raw)
In-Reply-To: <a8a1855047defb1760d72dcce5b0e7b7@coraid.com>

You can also use devdrawserver:

   https://github.com/mariusaeriksen/devdrawserver

Which acts as a devdraw proxy between two machines.

See also: http://9fans.net/archive/2012/04/207

marius.

On Fri, Oct 26, 2012 at 9:57 AM, erik quanstrom
<quanstro@labs.coraid.com> wrote:
>> Unfortunately acme doesn't have provisions for remote editing, however
>> you can edit any file on any file system you happen to import into
>> your namespace.
>>
>> If you wish to edit within Plan 9 natively, I'd look into one of the
>> many options to connect to a remote system using a file system
>> interface (http://www.plan9.bell-labs.com/wiki/plan9/Integration_with_other_OSs/index.html).
>>
>> If you are interested in using acme on other systems, rsc's plan9port
>> (http://swtch.com/plan9port/) could be of some use to you. acme-sac
>> (http://code.google.com/p/acme-sac/) is another possibility and
>> provides support for Windows as well.
>
> sftpfs works great in a pinch with stuart's ssh2.
>
> - erik
>



  reply	other threads:[~2012-10-26 17:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 15:34 KevinK
2012-10-26 16:02 ` Aram Hăvărneanu
2012-10-26 16:03 ` Steven Stallion
2012-10-26 16:05   ` Steven Stallion
2012-10-26 16:57   ` erik quanstrom
2012-10-26 17:51     ` marius a. eriksen [this message]
2012-10-26 16:26 ` yy
2012-10-29  9:46 ` KevinK
2012-10-29  9:46 ` KevinK

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPtk8tv91GKtMhbqG0X7h2Vke9QEHzuiTnOBni1QSwBtywOwbw@mail.gmail.com \
    --to=marius@monkey.org \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).