Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Fixed it. The problem is to do with the way that the <code>screen</code> <code>$TERM</code> handles italics. From the <a href="https://github.com/tmux/tmux/blob/master/FAQ" rel="nofollow noreferrer"><code>tmux</code> FAQ</a>:</p> <blockquote> <p>vim displays reverse video instead of italics, while less displays italics (or just regular text) instead of reverse. What's wrong?</p> </blockquote> <p>This matches my problem exactly. The <code>$PAGER</code> used by <code>man</code> is <code>less</code> by default - basically, <code>man</code> uses <code>less</code> to show the contents of the manual pages. In my case, <code>less</code> wasn't highlighting text, just showing regular text. </p> <p>The reason for this happening: </p> <blockquote> <p>Screen's terminfo description lacks italics mode and has standout mode in its place, but using the same escape sequence that urxvt uses for italics. This means applications (like vim) looking for italics will not find it and might turn to reverse in its place, while applications (like less) asking for standout will end up with italics instead of reverse.</p> </blockquote> <p>The solution is to make a new <code>terminfo</code> file for <code>tmux</code>, which lets it know that italics are supported. The solution's outlined in the (at time of writing) very, very bottom of the <code>tmux</code> FAQ. </p> <p>After creating the new <code>terminfo</code> file, in <code>tmux</code>: <code>C-b :source-file /absolute/path/to/.tmux.conf</code> (from <a href="https://superuser.com/questions/188491/tmux-disregarding-the-configuration-file">this SuperUser question</a>) - this <em>should</em> make <code>tmux</code> reload the <code>.tmux.conf</code> file. However, this didn't work for me, and the changes only applied after restarting the <code>tmux</code> server (close all <code>tmux</code> sessions, then re-open them). </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload