On Tue, Sep 26, 2017 at 12:39:19AM +0200, Axel Beckert wrote:
> Control: tag -1 - moreinfo + confirmed
> Control: found -1 4.1.0~20120320gitdb59704-7+deb7u1
> 
> Hi Cascardo,
> 
> Thadeu Lima de Souza Cascardo wrote:
> > I have this same problem with what seems to be valid UTF-8. One possible
> > reproduction test is running this on bash under screen.
> > 
> > echo -e '\xf0\x9f\x8d\x8c'
> > 
> > You will notice the extra space after that, which does not happen when
> > not under screen.
> 
> Thanks for the feedback and giving me a way to reproduce and test that
> (or at least a similar) issue. (And for the reminder that this bug
> report is still open. :-)
> 
> Unfortunately I can't reproduce it with your example.
> 
> I tried it with bash as well as with zsh inside a screen 4.6.1
> session, but everything looks fine.
> 

Sorry about that. My test was run with 4.5.0-6. It looks like 4.6.1 has
an updated Unicode support and that might have fixed it. As I run mutt
from screen from ssh from mosh, I realized mosh was to blame. When I
replaced it with ssh and used my system with screen 4.6.1-1, the problem
on mutt seemed to go away. So I would mark this as affecting 4.5.0-6,
but fixed at least in 4.6.1-1.

> I also tried
> 
> echo -e '\xf0\x9f\x8d\x8c'x
> 

I am using gnome-terminal, and if I don't use mosh, I see the banana. I
tested with both screen 4.5.0-6 and 4.6.1-1, and whenever using the
extra character, things seem to be printed fine (banana plus x, next
line rightly starting on the first column). If I only print the banana,
then 4.6.1-1 works fine, but 4.5.0-6 will have the prompt starting on
the second column. Tests were run with screen -U.

Interestingly, on some other versions of screen, without -U, I don't
see the banana, and adding extra characters will print them on the
previous line, overriding the previous prompt, which explains some of
the problems I see on mutt (an email with UTF-8 subject overriding the
previous email subject).

Thank you very much for maintaining screen. I will try to work with a
mosh bug now.

Cascardo.

> to see if there's a blank or similar directly behind that wide
> character (which shows up as a question mark inside a filled circle).
> 
> On which terminal did you happen to run into that? I have uxterm here.
> I also checked if any of my .screenrc settings could interfere, but
> nothing changed when commenting out any charset or terminal emulation
> related settings.
> 
> So I checked also gnome-terminal, but no luck there either.
> gnome-terminal showed me a banana btw., so this indeed seems to be
> valid UTF-8.
> 
> Then again, I ran into the original issue (spam displayed in mutt
> inside screen) at least with the screen version in Wheezy, so that one
> is definitely affected. (Your issue might or might not be the same
> issue. I'm not yet sure.) 
> 
> Next time I see such a case on Wheezy, I'll save a copy and check, if
> it's still present on Unstable.
> 
>               Regards, Axel
> -- 
>  ,''`.  |  Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
> : :' :  |  Debian Developer, ftp.ch.debian.org Admin
> `. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>   `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Reply via email to