all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Rohleder <mike@rohleder.de>
To: Leo Famulari <leo@famulari.name>
Cc: 53623@debbugs.gnu.org
Subject: [bug#53623] [PATCH] gnu: mosh: Fix path to binaries.
Date: Sun, 30 Jan 2022 11:14:55 +0100	[thread overview]
Message-ID: <87h79lbkdc.fsf@rohleder.de> (raw)
In-Reply-To: <YfWrVq9S+HZxY6rs@jasmine.lan> (Leo Famulari's message of "Sat, 29 Jan 2022 16:02:14 -0500")

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

Leo Famulari <leo@famulari.name> writes:
> Can you clarify the situation where it doesn't work? I'm using mosh as a
> server on Guix System and it's working for me.

Interesting. On my guix system it currently does this:

~$ mosh localhost
bash: line 1: mosh-server: command not found
Connection to localhost closed.
/gnu/store/8xfhfr75svf6lw3fl4pnj47f31hz04lr-mosh-1.3.2/bin/.mosh-real: Did not find mosh server startup message. (Have you installed mosh on your server?)

It's the same for remote guix systems.

Well, atleast the patch would save spawning a subshell ;)

-- 
On the eigth day, God started debugging

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

  parent reply	other threads:[~2022-01-30 10:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 14:29 [bug#53623] [PATCH] gnu: mosh: Fix path to binaries Michael Rohleder
2022-01-29 21:02 ` Leo Famulari
2022-01-29 22:27   ` Thiago Jung Bauermann via Guix-patches via
2022-01-30 10:14   ` Michael Rohleder [this message]
2022-01-30 18:35     ` Leo Famulari
2022-01-30 18:44       ` Michael Rohleder
2022-01-30 19:10         ` Leo Famulari
2022-01-30 22:32           ` Thiago Jung Bauermann via Guix-patches via
2022-03-06 21:39             ` Ludovic Courtès
2022-03-07  8:54               ` Michael Rohleder
2022-03-07 20:23                 ` bug#53623: " 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

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

  git send-email \
    --in-reply-to=87h79lbkdc.fsf@rohleder.de \
    --to=mike@rohleder.de \
    --cc=53623@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.