| View previous topic :: View next topic |
| Author |
Message |
krigstask
n00b
Joined: 27 Feb 2007
Posts: 40
Location: Rampova, Inkerimaa, Venämaa
|
 Posted: Mon Dec 24, 2012 3:59 pm Post subject: |
 |
|
| mv wrote: | | Having remote hosts which have ancient ncurses versions and thus do not know current TERM settings is kludgy. Thus to workaround this "bug" in the corresponding startup script on the machine (by setting to a wrong but at least recognized TERM) is probably the best which can be done. |
I was under impression that for host to know about TERM=rxvt-unicode256 it should have rxvt-unicode installed.
| Quote: | | Quote: | | Nope, it's just regular "login to X, start urxvt, run eix" scenario. |
What does echo $COLORFGBG output? If it outputs nothing, it is presumably unset in some of your startup scripts - this should be avoided. |
| Code: | % echo $COLORFGBG
15;default;0 |
|
|
| Back to top |
|
 |
mv
Advocate
Joined: 20 Apr 2005
Posts: 3226
|
| Posted: Mon Dec 24, 2012 4:38 pm Post subject: |
|
|
| krigstask wrote: | | I was under impression that for host to know about TERM=rxvt-unicode256 it should have rxvt-unicode installed. |
No: TERM only tells the application which escape sequences can be used and what they mean.
| Quote: | | Code: | % echo $COLORFGBG
15;default;0 |
|
Now I see: WIth XPM support, COLORFGBG has a different syntax which is currently not interpreted correctly by eix. As a workaround you can set
| Code: | | COLORFGBG_DARK=';0?[02-689]$ ;1[0-46]$ ;[a-km-vxz][a-z]*$' |
I guess this will be default in >=eix-0.27.7 |
|
| Back to top |
|
|
krigstask
n00b
Joined: 27 Feb 2007
Posts: 40
Location: Rampova, Inkerimaa, Venämaa
|
| Posted: Mon Dec 24, 2012 4:46 pm Post subject: |
|
|
| mv wrote: | | krigstask wrote: | | I was under impression that for host to know about TERM=rxvt-unicode256 it should have rxvt-unicode installed. |
No: TERM only tells the application which escape sequences can be used and what they mean. |
I know, but I distinctly remember ssh'ing to a up-to-date Gentoo system (but without urxvt) and failng because of $TERM. Fixed by installing rxvt-unicode. But maybe I made a mistake or misrecalled something.
| Quote: | | Quote: | | Code: | % echo $COLORFGBG
15;default;0 |
|
Now I see: WIth XPM support, COLORFGBG has a different syntax which is currently not interpreted correctly by eix. As a workaround you can set
| Code: | | COLORFGBG_DARK=';0?[02-689]$ ;1[0-46]$ ;[a-km-vxz][a-z]*$' |
I guess this will be default in >=eix-0.27.7 |
I think I'll stick with setting BG1=none for the time being. Good that it would be fixed, though, thanks! |
|
| Back to top |
|
|
mv
Advocate
Joined: 20 Apr 2005
Posts: 3226
|
| Posted: Sat Apr 06, 2013 8:15 am Post subject: |
|
|
Solarized users should be aware of an important change in app-portage/eix-0.28.4:
Please just set (or export from the shell) SOLARIZED=true (or light or dark). This will give you a special color scheme for solarized in 16 and 256 color terminals.
The previous recommendations to set TERM_ALT[0-3] or COLORSCHEME[0-3] for solarized users are obsolete!
If you have set these variable previously in your /etc/eixrc (or exported them), please remove them again! (It produces now suboptimal results.) |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
