> Configuring private keys in SSH for
> passphrase-less access is a better alternative.

And using ssh-agent[1] is even better than that. ;-)


-sth

[1]http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/ssh-agent.1

----- Original Message -----
> From: "Aaron S. Hawley" <[email protected]>
> To: [email protected]
> Sent: Wednesday, September 3, 2014 1:15:15 PM
> Subject: Re: remote cpu / local i/o
> 
> 
> 
> I thought Racket had remote execution as a feature.
> 
> Concerning Emacs, I know Tramp Mode gets a bad name, but I find that
> it is pretty well integrated across modes*. If you open a file using
> Tramp and run an Emacs command that does a system exec, it will be
> exec'd remotely on the machine.
> 
> 
> C-x C-f /[email protected]:foo.lsp RET
> C-u M-x inferior-lisp RET clisp RET
> 
> 
> If you get annoyed with password prompts in Tramp you can configure
> the expire time of the password. Configuring private keys in SSH for
> passphrase-less access is a better alternative.
> 
> 
> *The only issue you'll have is whether any 3rd-party REPL mode you
> use (something more modern than Inferior Lisp Mode) really supports
> Tramp as such.
> 
> 
> 
> 
> On Wed, Sep 3, 2014 at 10:36 AM, Anthony Carrico <
> [email protected] > wrote:
> 
> 
> 
> 
> On 09/03/2014 10:06 AM, Anthony Carrico wrote:
> > I was editing some local source-code in a local emacs buffer. The
> > emacs
> > mode (racket-mode) uses local programs (racket, raco) to compile,
> > run
> > tests, run the repl, etc. It would be nice to run that on a
> > (faster)
> > remote cpu, but the compilers need access to the local files, etc.
> > 
> > Is there some kind of weird utility that lets you run a local
> > command,
> > with access to the local file system, on a remote CPU by
> > intercepting
> > system calls or whatever (same architecture, of course)?
> > 
> 
> Just to anticipate some answers:
> * I know I could export the file system via nfs, and run ssh
> cpu-machine racket, but can it be done without exporting the
> filesystem?
> * I know I could move the files, and run ssh cpu-machine emacs -X.
> However, I didn't know about https://mosh.mit.edu , and someone
> pointed
> me to it. It looks very handy.
> 
> --
> Anthony Carrico
> 
> 
> 
> 
> 
> 
> --
> In general, we reserve the right to have a poor
> memory--the computer, however, is supposed to
> remember! Poor computer. -- Guy Lewis Steele Jr.
> 

Reply via email to