all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Michael Rohleder <mike@rohleder.de>
Cc: 53623@debbugs.gnu.org
Subject: [bug#53623] [PATCH] gnu: mosh: Fix path to binaries.
Date: Sun, 30 Jan 2022 13:35:12 -0500	[thread overview]
Message-ID: <YfbaYEVarzm9gsdj@jasmine.lan> (raw)
In-Reply-To: <87h79lbkdc.fsf@rohleder.de>

On Sun, Jan 30, 2022 at 11:14:55AM +0100, Michael Rohleder wrote:
> 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?)

I wonder, did you install mosh via config.scm? Or with `guix install
mosh`?

> It's the same for remote guix systems.
> 
> Well, atleast the patch would save spawning a subshell ;)

True, I think there's no harm with your patch.




  reply	other threads:[~2022-01-30 18:43 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
2022-01-30 18:35     ` Leo Famulari [this message]
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=YfbaYEVarzm9gsdj@jasmine.lan \
    --to=leo@famulari.name \
    --cc=53623@debbugs.gnu.org \
    --cc=mike@rohleder.de \
    /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.