unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Artyom Poptsov <poptsov.artyom@gmail.com>
To: guile-user-request@gnu.org
Cc: guile-user@gnu.org
Subject: Re: [ANN] Guile-SSH 0.8.0 released
Date: Tue, 01 Sep 2015 21:06:31 +0300	[thread overview]
Message-ID: <874mje10bc.fsf@elephant.savannah> (raw)
In-Reply-To: <mailman.95.1441123237.10692.guile-user@gnu.org> (guile-user-request@gnu.org's message of "Tue, 01 Sep 2015 12:00:37 -0400")

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

Hi Ludovic.

> Maybe this went unnoticed, but these are really awesome features!

Thanks!

> I think the manual should explicitly remind people that the REPL
> server must already be running on the remote machine.

I guess it is already mentioned in the manual.  From "(guile-ssh)
Distributed Forms":

  To make use of the procedures listed in this section you will need an
  SSH daemon and a GNU Guile REPL server both running on the remote
  host.

Or should I elaborate on this?

> I wonder if it would make sense to offer an alternate option where the
> calling machine invokes ?guile? on the remote side and talks to it on
> stdin; this could simplify some use cases.  WDYT?

Sure enough, we can call 'guile' on the remote side using
'channel-request-exec' before using of procedures from (ssh dist).  That
looks like a great idea, I need to think about the implementation.

> However, this:

>   (let ((session (make-session #:user "ludo" #:host "xxx")))
>     (connect! session)
>     (userauth-agent! session)
>     (with-ssh (make-node session)
>               (use-modules (ice-9 ftw))
>               (scandir "/")))

> returns only two values, the language and the module.

Thank you for reporting that bug, fixed in 76d8df2 on the master.  Also
I fixed parsing of RREPL errors, in c7b6a79.

Please check if it works for you.

- Artyom

-- 
Artyom V. Poptsov <poptsov.artyom@gmail.com>;  GPG Key: 0898A02F
Home page: http://poptsov-artyom.narod.ru/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

       reply	other threads:[~2015-09-01 18:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.95.1441123237.10692.guile-user@gnu.org>
2015-09-01 18:06 ` Artyom Poptsov [this message]
2015-09-02 19:55   ` [ANN] Guile-SSH 0.8.0 released Ludovic Courtès
     [not found] <mailman.71.1438704082.32144.guile-user@gnu.org>
2015-08-05 13:46 ` Artyom Poptsov
2015-08-03 23:03 Artyom Poptsov
2015-09-01 12:08 ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=874mje10bc.fsf@elephant.savannah \
    --to=poptsov.artyom@gmail.com \
    --cc=guile-user-request@gnu.org \
    --cc=guile-user@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).