Description of problem: After upgrading to F22, all terminals (GNOME Terminal and the real xTerm) are very broken using the recommended/standard TERM setting, screen-256color Version-Release number of selected component (if applicable): tmux-1.9a-5.fc22.x86_64 How reproducible: Since F22, I can't figure out how to fix it. Steps to Reproduce: 1. start tmux 2. start alpine or finch or wyrd or anything that can use the color terminal 3. OR, just run 'man tmux' Actual results: The tell-tale symptom is that bold text is now bold, but italicized, instead. Other artefacts have also been noticed, i.e. terminal line-drawings are sometimes badly messed up. Expected results: Everything was fine in F21, so I don't see why this should be any different. Additional info: The problem occurs with TERM=screen, the default, and TERM=screen-256color, which I thought was the recommended setting. At least that's what I learned from the guys on #tmux.
Correction: tell-tale sign is that *reverse* characters are show as italicized. Sorry. I'm very confused. Please help.
Read up on this; it's a long story but, apparently, well known. I don't know why ncurses pkg was updated with this change, but tmux was not. Seems like the terminfo has always been wrong and the current version is "correct," despite the fact that screen, itself, does *not* respect the new capability. Makes no sense, whatsoever. In any case, tmux had to be patched for this specific issue! Please update tmux with this patch.
Hi paul. Which "existing patch" are you referring to?
I only know it as the fix for 'screen' terminfo change. TMUX refers to it as "standout instead of italics for SGR3". Oh, here's a git ref # and msg: f60d88cd24: use standout instead of italics for SGR3, like screen does Does that help? I figured someone on the tmux dev side would recognize it; it got quite a bit of coverage from Debian & Ubuntu folks. See post 82, here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756353#82 They cherry-picked it onto the 2.0 branch, but I'm hoping you can pick it on 1.9 or maybe rev tmux? Whatever you can do would be great. BTW, two workarounds are mentioned: 1) use the 'terminal_override' setting to give the traditional behavior (see bug for details). 2) create your own terminfo. (See tmux docs under "vim" and "italics" for a script.) I can confirm this works, but what a crazy workaround.
BTW, workaround #2 has a major drawback, I found: it doesn't scale; every system I ssh into breaks because it doesn't have my special terminfo file. I knew that was a terrible idea. I haven't tried it, but now I can confidently recommend #1, instead.
Ugh, what a headache. I couldn't get workaround #1 to work either. I see that the example in the referenced bug applies to 'xterm*' terminals, but that makes no sense whatsoever since the problem doesn't occur with TERM=xterm. 'xterm' is fine, 'screen' is what is changed. If someone could explain the proper override string, that would be great. I can't figure out how to use terminal-override to fix this.
I'm having the same problem. Using `TERM=xterm alpine` solves that one particular problem tolerably, but tmux is broken with the default TERM=screen for man, less, and everything else to a greater or lesser degree.
*** Bug 1252744 has been marked as a duplicate of this bug. ***
I think this is fixed in F24. Do others agree? If someone knows how this got fixed, I'm very curious. Patch was there a year ago but didn't make it into new version 2.1-2 packaged in F23.
Yes, it's working for me in F24. TERM=screen with alpine, man, and less all work fine now. Thanks.
*** Bug 1247495 has been marked as a duplicate of this bug. ***
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.