blinksh / blink

Blink Mobile Shell for iOS (Mosh based)
https://blink.sh
GNU General Public License v3.0
6.19k stars 578 forks source link

mosh session drawn over Blink shell #778

Open treyharris opened 5 years ago

treyharris commented 5 years ago

This issue appears to be the converse of #731 — rather than having Blink shell output appearing in the middle of the active Mosh session which continues to receive input, I have the Blink shell doing I/O while the active Mosh session continues to update its output, but I can’t interact with it.

Here’s a video clip showing the issue: YouTube link

Note that at the start of the video, the time is after 18:26:51 but once it hits 18:27, the clock of the remote program in the Mosh session (visible on the far left of the bottom blue status bar) updates and the cursor moves back to where it would be in the Mosh session, but the blink shell is what’s accepting input; at 3 seconds in when I press d key, to type date, the cursor jumps, and the previously-displayed date output lines and blink> input lines disappear.

The circumstances of this happening are:

  1. I switched to another iPad app and switched back.
  2. The Mosh session, which had filled the screen, now occupied only the upper-left, as can be seen in the video. This resizing happened by reducing the rows and columns of text, not by shrinking the font size.
  3. If I tap in the window, terminal mouse tap control characters appear as text input to the blink> shell. This does not happen in other Blink shells, even after exiting a Mosh session that has enabled mouse input.

This has happened to me a number of times, but I can’t reproduce it reliably.

pedrosanta commented 5 years ago

I think I have this happening to me too.

Mosh session with Tmux, switch to another app, switch back, and terminal/text is all garbled, and have to close Blink tab and kill the detached mosh session.

andrius commented 5 years ago

I can also confirm that, however that does not happening too often, in my case its random issue

carloscabanero commented 5 years ago

I have seen this too, randomly. It started to happen when we moved to the iOS system way of handling descriptors. I think there is something not properly done there. We have to review and prioritize for 13.