LinuxQuestions.org - Elvis and rxvt-unicode/tmux/screen

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Elvis and rxvt-unicode/tmux/screen (https://www.linuxquestions.org/questions/slackware-14/elvis-and-rxvt-unicode-tmux-screen-4175609745/)

Elvis and rxvt-unicode/tmux/screen

Slackware64-current - fully up to date

Somewhere in this development (at least as far as I can tell) Elvis has started misbehaving. Nothing totally breaking, but still misbehaving. I use rxvt-unicode with tmux. Under tmux $TERM reports:

Code:

screen-256color

This causes Elvis to print:

Code:

must set normal colors first

I don't recall this happening leading up to the release of 14.2. If I had to take a bad guess I would imagine it happened around here:

Code:

Sat Dec 24 02:36:05 UTC 2016

...

l/libtermcap-1.2.3-x86_64-7.txz:  Removed.

  Replaced by equivalent functionality in the ncurses package.

But that is just a bad guess. I have an elvis.clr that I had tinkered with at one point because it did funny things to the comments under rxvt-unicode. If I comment out that file things seem to work okay under screen-256color but then rxvt-unicode gets things like underlined comments.

Any help or insight would be greatly appreciated.

Edit: I created a function in my .kshrc to call Elvis as such:

Code:

case "$TERM" in

linux*) elvis "$@"

*) TERM=xterm elvis "$@"

esac

This makes Elvis work fine, but it seems "hacky". I'm hoping there is a cleaner solution.

Can you try adding something like this in your ~/.elvisrc ? adjusting to your needs.

Quote:

color normal white on black
color comment brown
color keyword navyblue
color selection black on white
color spell red
color selection white on black

Quote:

Originally Posted by jmccue (Post 5734333)

Can you try adding something like this in your ~/.elvisrc ? adjusting to your needs.

I gave that a shot exactly as typed up and with a few variations and still the same results. It's not a huge deal breaker. I have Elvis in a working state. Thanks for your reply.

Interesting, I am not on current but I heard it now defaults to termio. Does this file exist ?

/usr/share/terminfo/x/xterm-256color

In rxvt-unicode on my -current system, I see

Code:

bash-4.4$ echo $TERM

rxvt-unicode-256color

I do not get the error that you report.
For my setup, see https://www.linuxquestions.org/quest...6/#post5685789

Terminfo entries may not be correct

I have the same issue, with this program and another, running under screen. Some of the files that are in the terminfo database are listed as "32-bit terminfo entry". These do not work.

Code:

screen-256color: Compiled 32-bit terminfo entry "screen-256color"

rxvt-unicode-256color: Compiled terminfo entry "rxvt-unicode-256color"

Setting TERM to "screen-w" works for me. The reason I bring this up now, is that there are many files in the terminfo database that have this issue. Maybe the database needs updating? For example in the "s" directory:

Code:

s> file * | grep 32

screen-256color:        Compiled 32-bit terminfo entry "screen-256color"

screen-256color-bce:    Compiled 32-bit terminfo entry "screen-256color-bce"

screen-256color-bce-s:  Compiled 32-bit terminfo entry "screen-256color-bce-s"

screen-256color-s:      Compiled 32-bit terminfo entry "screen-256color-s"

screen.konsole-256color: Compiled 32-bit terminfo entry "screen.konsole-256color"

screen.mlterm-256color:  Compiled 32-bit terminfo entry "screen.mlterm-256color"

screen.putty-256color:  Compiled 32-bit terminfo entry "screen.putty-256color"

screen.vte-256color:    Compiled 32-bit terminfo entry "screen.vte-256color"

screen.xterm-256color:  Compiled 32-bit terminfo entry "screen.xterm-256color"

scrt:                    Compiled 32-bit terminfo entry "scrt"

st-256color:            Compiled 32-bit terminfo entry "st-256color"

st-direct:              Compiled 32-bit terminfo entry "st-direct"