-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues using mosh #43
Comments
Hm, I would say that is something on mosh's end. I know mosh does some trickery to quickly paint stuff in a seamless manner, so it's not difficult to fathom that something like that is messing this up. I don't think there is anything I can do, because the ASCII Shibe already has color codes surrounding every single cell. There is nothing I can improve to a higher resolution in regard to the image. I also note that most of the colors that are messing Shibe up is not present anywhere else on the screen, which is peculiar. Is it the same breakage everytime? What happens if you find Either way, I suggest that you open an issue with mosh and reference to this one. They might figure something cool out. :> |
Just like #44, I don't think there is anything doge can do about this since this is in a very specific environment. Closing this one as well. Thanks for reporting it anyway! |
doge.txt combines multiple 256color rendition changes in the same SGR sequence, e.g., `ESC [ 48;5;179; 38;5;100 m` to change both the background and foreground color. The xterm-256color terminfo entry requires (and mosh enforces) that these be in separate escapes. Example: `echo -e "setab 179\nsetaf 100" | tput -S | od -c` generates `ESC [ 48;5;179 m ESC [ 38;5;100 m`. File converted with: perl -0777 -wpe 's{;38;}{m\033[38;}g' doge.txt Fixes Olivia5k#43. (Also reported at mobile-shell/mosh#519)
doge.txt combines multiple 256color rendition changes in the same SGR sequence, e.g., `ESC [ 48;5;179; 38;5;100 m` to change both the background and foreground color. The xterm-256color terminfo entry requires (and mosh enforces) that these be in separate escapes. Example: `echo -e "setab 179\nsetaf 100" | tput -S | od -c` generates `ESC [ 48;5;179 m ESC [ 38;5;100 m`. File converted with: perl -0777 -wpe 's{;38;}{m\033[38;}g' doge.txt Fixes #43. (Also reported at mobile-shell/mosh#519)
I'm not sure if this is a glitch with mosh or with doge.py, but whenever I connect using mosh, the pretty doge is completely butchered. I've tested it using both ssh and mosh on the same terminal with identical settings, but only mosh does it.
With SSH, it loads fine. However, with mosh...
Nothing huge (doge doesn't make or break my terminal experience), but I figured it was worth reporting.
The text was updated successfully, but these errors were encountered: