Warp
Warp copied to clipboard
warpdotdev
Support "warpified" mosh sessions
Describe the solution you'd like?
https://mosh.org/ is a cool replacement for ssh. Would be great if Warp blocks and input worked with it.
Is your feature request related to a problem? Please describe.
No response
Additional context
No response
From Procrastinatus via Discord: https://discord.com/channels/851854972600451112/852249738002956311/950869902804271156 Not a bug, but found these interesting test cases for handling prompt input:
echo -e "abc\n\0314\0202\ndef"
echo -e "\033(0"
echo -e "xyz\033[2;2H\0314\0202\nhello"
(cases described here: https://mosh.org/#techinfo )
I left a comment on #272 which error message is the same as I have, and I would like to point out that mosh support is a blocking issue for me: mosh is such an enhancement over SSH that I cannot imagine using a tool that does not support mosh.
Including @delahondes comment here: Same issue here with Ubuntu 20.04, mosh close the connection with a message about LOCALE (not the case with another terminal):
The locale requested by LC_CTYPE=UTF-8 isn't available here.
Running `locale-gen UTF-8' may be necessary.
The locale requested by LC_CTYPE=UTF-8 isn't available here.
Running `locale-gen UTF-8' may be necessary.
mosh-server needs a UTF-8 native locale to run.
Unfortunately, the local environment (LC_CTYPE=UTF-8) specifies
the character set "US-ASCII",
The client-supplied environment (LC_CTYPE=UTF-8) specifies
the character set "US-ASCII".
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=fr_FR.UTF-8
LANGUAGE=
LC_CTYPE=UTF-8
LC_NUMERIC="fr_FR.UTF-8"
LC_TIME="fr_FR.UTF-8"
LC_COLLATE="fr_FR.UTF-8"
LC_MONETARY="fr_FR.UTF-8"
LC_MESSAGES="fr_FR.UTF-8"
LC_PAPER="fr_FR.UTF-8"
LC_NAME="fr_FR.UTF-8"
LC_ADDRESS="fr_FR.UTF-8"
LC_TELEPHONE="fr_FR.UTF-8"
LC_MEASUREMENT="fr_FR.UTF-8"
LC_IDENTIFICATION="fr_FR.UTF-8"
LC_ALL=
Connection to xxxxxxxxx closed.
/usr/local/bin/mosh: Did not find mosh server startup message. (Have you installed mosh on your server?)
The suggested command locale-gen UTF-8 is not valid: Error: 'UTF-8' is not a supported language or locale
PS I must say that this issue is blocking for me, mosh is such an enhancement for me over plain ssh that I cannot imagine working with a tool that does not support it.
To make mosh work, I had to add export LC_CTYPE="de_DE.UTF-8" in my OSX .bashrc (must be "fr_FR" for you then)
As I seldom use SSH but only Mosh and TMux (I am usually connected to 4+ server each with multiple tmux screens) I found Warp, not a replacement for my iTerm2 setup. This may change ft Warp could wrap mosh (and would be even better when TMux could be wrapped too), but I guess that is not likely to happen.
Thanks Hans, I confirm it works with export LC_CTYPE="fr_FR.UTF-8" in my OSX .bashrc. I read precisely my thoughts in your words, but it is good that some people invent new things and try to adapt them to different usages. Same setup for me, I feel at home with what you describe ;-) (I am in bioinformatics). Except I replaced iTerm2 by kitty Terminal which I find lighter and more configurable (and as a spare time BSD user, I tend to prefer screen to tmux).
Raynald
Hi there! Are there any updates? Mosh is working perfectly fine, however, it'd be nice to know what to expect in terms of Warp-specific features related to this utility.
Thanks!
@0xb1b1 There isn't anything formally planned for the next couple of months but will swing this by our team.
It was frustrating to watch my own row of mosh without the support of the warp command prompt :(
The effort around this is pretty big and we also would have to make changes on Mosh's side. There isn't anything on deck for the short term. Apologies!
Does Warp work with any other utilities that address network flakiness when using ssh? I see #897 and #1981 are open for the only alternative software of which I'm aware.
@stackptr This is a really great question to which I'd also like to know the answer.
It's really frustrating that every solution (I've found so far) to flaky SSH connections or regular VPN timeouts (12 hour limit in my case) is incompatible with Warp because they all use some kind of full screen mode or frame buffer that takes over a terminal's output.
In the meantime, continuing to use Warp with SSH means I have choose to either spend a bunch of time EVERY DAY properly disconnecting from all my remote work systems at the end of the day, or start every work day recovering broken terminals; I have young kids, thus my work days usually end abruptly, so it's usually the ladder, which is more painful. Either way, there's a lot of pain due to connectivity loss. I'm thinking of just installing mosh anyway, giving up most (all?) of Warp's best features to avoid the daily frustration and costly hit to productivity.
I'm loving Warp, but I'm not loving that it doesn't address the one value proposition that new SSH/terminal apps are usually designed to address: connectivity interruptions to remote systems.
I'm hoping someone can chime in with a workable (preserves some of Warp's features) solution to connection interruptions, or the Warp devs (who are seriously working hard to improve things regularly!) might prioritize the issue in some way to make life better.
A workaround with eternal terminal + ssh https://github.com/warpdotdev/Warp/discussions/501#discussioncomment-13434422
