Users of the Mutt mail reader

Aaron Griffin | 31 Aug 2006 22:55

Re: 256 colors

On 8/24/06, cga2000 <cga2000 <at> optonline.net> wrote:
> How can I have mutt display the 256 colors my xterm is capable of..?

The problem is that mutt doesn't use numeric colors, it uses textual
colors.  If there was a way to say "use color 76" then this would work
great.

headers

Kyle Wheeler | 1 Sep 2006 00:15

Re: 256 colors


On Thursday, August 31 at 03:55 PM, quoth Aaron Griffin:
> On 8/24/06, cga2000 <cga2000 <at> optonline.net> wrote:
>> How can I have mutt display the 256 colors my xterm is capable of..?
>
> The problem is that mutt doesn't use numeric colors, it uses textual
> colors.  If there was a way to say "use color 76" then this would work
> great.

There is.

    color index color8 color1 ~D

Works fine for me.

~Kyle
--

-- 
Those who can make you believe absurdities can make you commit 
atrocities.
                                                           -- Voltaire

headers

Frank Hart | 26 Aug 2006 02:07

Re: 256 colors

On Thu, Aug 24, 2006 at 05:03:46PM -0400, cga2000 wrote:
> How can I have mutt display the 256 colors my xterm is capable of..?

By the way, how is this question different to the one you asked in
april?

--

-- 
Frank Hart

headers

cga2000 | 27 Aug 2006 17:05

Re: 256 colors

On Fri, Aug 25, 2006 at 08:07:18PM EDT, Frank Hart wrote:
> On Thu, Aug 24, 2006 at 05:03:46PM -0400, cga2000 wrote:

> > How can I have mutt display the 256 colors my xterm is capable of..?
> 
> By the way, how is this question different to the one you asked in
> april?

So *that's* where I got the idea ..

Totally slipped my mind .. I only remembered that I had somehow gotten
it to work .. but not quite .. 

I must have spent over and hour googling for the doc/howto where I
_thought_ I had found that mutt supported 256 colors .. kicking myself
for not having saved it to my HD ..

Thanks

cga

headers

Frank Hart | 26 Aug 2006 02:00

Re: 256 colors

On Thu, Aug 24, 2006 at 05:03:46PM -0400, cga2000 wrote:
> How can I have mutt display the 256 colors my xterm is capable of..?

export TERM=xterm-256colors

I had a small issue where <BackSpace> didn't work anymore in mutt. xterm
had a different keycode for it:

$ infocmp xterm-256color xterm | grep kbs
       kbs: '^H', '\177'.

But I've changed the kbs keycode in xterm-256colors so it's the same as
xterm:

$ export TERM=256color
$ infocmp -L > .terminfo/x/xterm-256color
$ vi .terminfo/x/xterm-256color
$ tic .terminfo/x/xterm-256color

--

-- 
Frank Hart

headers

cga2000 | 27 Aug 2006 16:58

Re: 256 colors

On Fri, Aug 25, 2006 at 08:00:52PM EDT, Frank Hart wrote:
> On Thu, Aug 24, 2006 at 05:03:46PM -0400, cga2000 wrote:
> > How can I have mutt display the 256 colors my xterm is capable of..?
> 
> export TERM=xterm-256colors
> 
xterm-256color does not play well with gnu/screen .. 

gnu/screen sets the TERM variable to screen-bce but mutt does not
recognize this as a 256color-capable terminal.

As a result entering the following:

:color tree color123 black

.. returns:

123: color not supported by term

Not sure where I go from there.  

Sounds like the easiest would be to infocmp screen-bce and tic it back
as xterm-256color somewhere else .. and then force gnu/screen (mutt ..
vim .. etc.) to use that instead. 

> I had a small issue where <BackSpace> didn't work anymore in mutt. xterm
> had a different keycode for it:
> 
> $ infocmp xterm-256color xterm | grep kbs
>        kbs: '^H', '\177'.

(Continue reading)

headers

Alain Bench | 30 Aug 2006 16:25

Re: 256 colors

Hello,

 On Sunday, August 27, 2006 at 10:58:10 -0400, cga2000 wrote:

> the easiest would be to infocmp screen-bce and tic it back as
> xterm-256color somewhere else

    No: That would be a mistake. To work properly, such setup needs both
the correct TERM=xterm-256color for the real terminal outside and under
Screen, and a TERM=screen-256color (or variant) for inside Screen.
GNU screen does translations between the underlying real terminal, and
the virtual terminal it implements.

| screen-256color-bce|GNU Screen with 256 colors and BCE,
|	sgr0=\E[m^O,
|	ccc <at> , initc <at> ,
|	use=xterm+256color,
|	use=screen-bce,

Bye!	Alain.
--

-- 
When you want to reply to a mailing list, please avoid doing so from a
digest. This often builds incorrect references and breaks threads.

headers

cga2000 | 31 Aug 2006 06:01

Re: 256 colors

On Wed, Aug 30, 2006 at 10:25:55AM EDT, Alain Bench wrote:
> Hello,
> 
>  On Sunday, August 27, 2006 at 10:58:10 -0400, cga2000 wrote:
> 
> > the easiest would be to infocmp screen-bce and tic it back as
> > xterm-256color somewhere else

>     No: That would be a mistake. To work properly, such setup needs
>     both the correct TERM=xterm-256color for the real terminal outside
>     and under Screen, and a TERM=screen-256color (or variant) for
>     inside Screen.  GNU screen does translations between the
>     underlying real terminal, and the virtual terminal it implements.

Well .. as a temporary solution .. what I had in mind was running the
underlying xterm with the original TERM=xterm-256color and my screen
terminal sessions with TERM set to my doctored xterm-256color -- alias
screen-bce.

The more I think about it this is likely to cause problems. Especially
since you tell me that gnu/screen accesses both the "screen" terminfo
entry and the undelying xterm's.

> | screen-256color-bce|GNU Screen with 256 colors and BCE,
> |	sgr0=\E[m^O,
> |	ccc <at> , initc <at> ,
> |	use=xterm+256color,
> |	use=screen-bce,

I understand that:

(Continue reading)

headers

Alain Bench | 31 Aug 2006 14:50

Re: 256 colors

 On Thursday, August 31, 2006 at 0:01:57 -0400, cga2000 wrote:

> you tell me that gnu/screen accesses both the "screen" terminfo entry
> and the undelying xterm's.

    More precisely Screen reads the TERM=xterm (or whatever) terminfo
for the real underlying terminal on one side, and implements a mostly
hardcoded virtual terminal on the other side. Apps inside Screen run in
this virtual term, and need an appropriate terminfo describing it:
TERM=screen and friends.

>>| screen-256color-bce|GNU Screen with 256 colors and BCE,
>>|	sgr0=\E[m^O,
>>|	ccc <at> , initc <at> ,
>>|	use=xterm+256color,
>>|	use=screen-bce,
> I understand that:

    Reverse: Values declared first win. Note that a "+" in entry name
denotes a building block, not a full usable entry. So this
screen-256color-bce is: screen-bce, with added 256 colors definitions
(colors#, pairs#, setaf/setab, ccc, and initc), wiped ccc and initc
(customizing color palette is not implemented by Screen), and finally
modified attributes-off to also turn off line drawing characters.

> It looks like mutt is aware of certain 256-capable terminals based on
> their terminfo name.

    Not on the entry name itself. Mutt and all well written apps should
be checking the corresponding terminfo content:

(Continue reading)

headers

cga2000 | 4 Sep 2006 23:09

Re: 256 colors

On Thu, Aug 31, 2006 at 08:50:25AM EDT, Alain Bench wrote:
>  On Thursday, August 31, 2006 at 0:01:57 -0400, cga2000 wrote:

Apologies for not replying earlier.

>     More precisely Screen reads the TERM=xterm (or whatever) terminfo
> for the real underlying terminal on one side, and implements a mostly
> hardcoded virtual terminal on the other side. Apps inside Screen run in
> this virtual term, and need an appropriate terminfo describing it:
> TERM=screen and friends.

> 
> >>| screen-256color-bce|GNU Screen with 256 colors and BCE,
> >>|	sgr0=\E[m^O,
> >>|	ccc <at> , initc <at> ,
> >>|	use=xterm+256color,
> >>|	use=screen-bce,
> > I understand that:
> 
>     Reverse: Values declared first win. 

What confused me was that in that event the "use=" statements should
reflect the order of the successive layers in my "stack" .. IOW, the
xterm being at the bottom, the "use=screen-bce" should come before the
"use=xterm" .. I'm still unclear as to why this should not be.

> Note that a "+" in entry name denotes a building block, not a full
> usable entry. 

I copied/pasted the above with "use=xterm+256color" and tic replied with

(Continue reading)

headers

Alain Bench | 6 Sep 2006 14:05

Re: 256 colors

 On Monday, September 4, 2006 at 17:09:58 -0400, cga2000 wrote:

> On Thu, Aug 31, 2006 at 08:50:25AM EDT, Alain Bench wrote:
>> Reverse: Values declared first win.
> the "use=" statements should reflect the order of the successive
> layers in my "stack" .. IOW, the xterm being at the bottom, the
> "use=screen-bce" should come before the "use=xterm" .. I'm still
> unclear as to why this should not be.

    Because then the 8 colors definitions of screen would overrule the
256 colors defs. Which is not the goal.

> tic replied with an "xterm+256color" terminfo not found

    Old terminfo database: Either upgrade, or tic this block first:

| xterm+256color|Xterm-like 256 colors definitions,
|	colors#256, pairs#32767,
|	setab=\E[%?%p1%{8}%<%t4%p1%d%e%p1%{16}%<%t10%p1%{8}%-%d%e48;5;%p1%d%;m,
|	setaf=\E[%?%p1%{8}%<%t3%p1%d%e%p1%{16}%<%t9%p1%{8}%-%d%e38;5;%p1%d%;m,
|	setb <at> , setf <at> ,

> I had to change that to "use=xterm-256color" to match the actual
> terminfo entry on my system.

    Not good: Those entries are completely different.

> the "indicator" line in the index is "interrupted"

    And with a recreated proper screen-256color-bce?

(Continue reading)

headers

cga2000 | 9 Sep 2006 16:35

Re: 256 colors

On Wed, Sep 06, 2006 at 08:05:24AM EDT, Alain Bench wrote:
>  On Monday, September 4, 2006 at 17:09:58 -0400, cga2000 wrote:

[..]

> > the "use=" statements should reflect the order of the successive
> > layers in my "stack" .. IOW, the xterm being at the bottom, the
> > "use=screen-bce" should come before the "use=xterm" .. I'm still
> > unclear as to why this should not be.

> Because then the 8 colors definitions of screen would overrule the 256
> colors defs. Which is not the goal.

Found that by reversing the two entries.

> > tic replied with an "xterm+256color" terminfo not found
> 
> Old terminfo database: Either upgrade, or tic this block first:
> 
> | xterm+256color|Xterm-like 256 colors definitions,
> |	colors#256, pairs#32767,
> |	setab=\E[%?%p1%{8}%<%t4%p1%d%e%p1%{16}%<%t10%p1%{8}%-%d%e48;5;%p1%d%;m,
> |	setaf=\E[%?%p1%{8}%<%t3%p1%d%e%p1%{16}%<%t9%p1%{8}%-%d%e38;5;%p1%d%;m,
> |	setb <at> , setf <at> ,
> 
> > I had to change that to "use=xterm-256color" to match the actual
> > terminfo entry on my system.
> 
> Not good: Those entries are completely different.
>

(Continue reading)

headers

Alain Bench | 9 Oct 2006 22:36

Re: 256 colors

Hello,

 On Saturday, September 9, 2006 at 10:35:00 -0400, cga2000 wrote:

> shouldn't your new screen [screen-256color-bce] entry be "officially"
> added to the terminfo database so that others benefit by your fixing
> this annoying issue?

    Done: Since last Saturday, the official terminfo database includes
8 new generic screen entries, combinations around 16 and 256 colors with
or without BCE and status line. Thanks go to testers, and to Thomas.

Bye!	Alain.
--

-- 
Give your computer's unused idle processor cycles to a scientific goal:
The Folding <at> home project at <URL:http://folding.stanford.edu/>.

headers

Henry Nelson | 13 Sep 2006 03:45

Re: 256 colors

On Sat, Sep 09, 2006 at 10:35:00AM -0400, cga2000 wrote:
> happened .. To fix the "bce issue" I set TERM to terminfo entries that
> were not 256-color capable on terminals (screen/xterm) that _did_ have
> the capability ..  and then used the config files where possible (vim,
> eg.) to inform the apps of the terminal's real color capabilities ..

Could you elaborate (explain with concrete examples) this section.  I
don't really understand what the "bce issue" is, nor what "the config
files" refer to.  TIA

For the record, my scenerio is:
Use Mutt and other apps within GNU Screen (--enable-colors256) on NetBSD
server.  Shell is csh.  TERMCAP and TERMINFO (location of description
databases) are set in .login, but TERM is not set.  The terminal emulation
is PuTTY on WindowsXP, and PuTTY is set to pass "putty-256c" to the shell.
(The name of Alain's "putty-256color" was shortened in source file before
tic'ing so that screen can be invoked within screen.)  `setenv | grep TERM`
output is: "TERM=screen.putty-256c".  In $HOME/.screenrc I have "termcapinfo
putty* vb <at> " and "termcapinfo putty* hs <at> " on separate lines.  I do not set
"term" in $HOME/.screenrc.  (I used to, but it didn't seem to matter so I
commented that line out.)

Other than not being able to print via vtprint or lpansi, the above setup
seems to be working okay.  Nevertheless, any and all advice and/or suggestions
very welcome and appreciated.

--

-- 
henry nelson
  WWW_HOME=http://yuba(dot)ne(dot)jp/(tilde)home/

(Continue reading)

headers

Alain Bench | 13 Sep 2006 15:40

Re: 256 colors

Hello Henry,

 On Wednesday, September 13, 2006 at 10:45:14 +0900, Henry Nelson wrote:

> PuTTY is set to pass "putty-256c" to the shell [...] I do not set
> "term" in $HOME/.screenrc [...] `setenv | grep TERM` output is:
> "TERM=screen.putty-256c".

    Suboptimal: To cleanly exploit the 256 colors, you are supposed to
have also a 256-aware TERM inside Screen. The most natural way is to set
"term" in screenrc. For you:

| term screen-256color-bce

    ...then if it's available (see bottom note), Screen will autoexport
the longish specialized entry:

| TERM=screen-256color-bce.putty-256c

    ...which should work better, but might need some more name
shortening efforts (short aliases, symbolic links, whatever). Your goal
is to have no more "$TERM too long - sorry." errors, and still have:

| $ infocmp -1 | egrep "bce|colors|kf20"
|	bce,
|	colors#256,
|	kf20=\E[34~,

    Note to others: Henry has an experimental customized terminfo
database. Nobody else has the same entries. With the same settings,

(Continue reading)

headers

cga2000 | 13 Sep 2006 07:16

Re: 256 colors

On Tue, Sep 12, 2006 at 09:45:14PM EDT, Henry Nelson wrote:
> On Sat, Sep 09, 2006 at 10:35:00AM -0400, cga2000 wrote:
> > happened .. To fix the "bce issue" I set TERM to terminfo entries that
> > were not 256-color capable on terminals (screen/xterm) that _did_ have
> > the capability ..  and then used the config files where possible (vim,
> > eg.) to inform the apps of the terminal's real color capabilities ..
> 
> Could you elaborate (explain with concrete examples) this section.  I
> don't really understand what the "bce issue" is, nor what "the config
> files" refer to.  TIA

The "bce issue" refers to a problem with stuff like status lines -- say
white text on a blue background..  What I have observed is that I
"lose" the background color .. or rather it stops where text stops.

Difficult to describe but you can check out the mutt screenshot I
posted recently for a sample.

This is somewhat annoying when for instance you are in the mutt index
with the "current message" highlighted..  When you move up and down the
index, the "indicator" line (? .. I think that's what it's called ..
no time to check ..) is broken somewhere in the middle and the two
separate parts of the line change lengths depending on the length of
the current message's subject for instance.

It's not only ugly but it also becomes rather annoying after a while.

I have no understanding of terminals in general and this particular

(Continue reading)

headers

Henry Nelson | 14 Sep 2006 03:55

Re: 256 colors

On Wed, Sep 13, 2006 at 01:16:06AM -0400, cga2000 wrote:
> > don't really understand what the "bce issue" is, nor what "the config
> > files" refer to.  TIA
> 
> The "bce issue" refers to a problem with stuff like status lines -- say
> white text on a blue background..  What I have observed is that I
> "lose" the background color .. or rather it stops where text stops.
> 
> Difficult to describe but you can check out the mutt screenshot I
> posted recently for a sample.
> 
> This is somewhat annoying when for instance you are in the mutt index
> with the "current message" highlighted..  When you move up and down the
> index, the "indicator" line (? .. I think that's what it's called ..
> no time to check ..) is broken somewhere in the middle and the two
> separate parts of the line change lengths depending on the length of

Perfect!  Thanks very much.  When I very first started using Mutt, I
had this problem, but over time it "went away" without my ever knowing
why.

> least Alain B's terminfo took care of this problem.
[...]
> I then managed to get Vim and ELinks (again a 256-color capable version)
> to use the 256 colors that my hardware was capable or (xterm configured
> with 256 colors) by "saying so" in their respective config files.  And
> both apps were kind enough to oblige.
> 
> mutt, OTOH only cares about what is specified in the terminfo entry

(Continue reading)

headers

cga2000 | 15 Sep 2006 08:16

Re: 256 colors

On Wed, Sep 13, 2006 at 09:55:23PM EDT, Henry Nelson wrote:
> On Wed, Sep 13, 2006 at 01:16:06AM -0400, cga2000 wrote:

[..]

> > This is somewhat annoying when for instance you are in the mutt index
> > with the "current message" highlighted..  When you move up and down the
> > index, the "indicator" line (? .. I think that's what it's called ..
> > no time to check ..) is broken somewhere in the middle and the two
> > separate parts of the line change lengths depending on the length of
> 
> Perfect!  Thanks very much.  When I very first started using Mutt, I
> had this problem, but over time it "went away" without my ever knowing
> why.

Good .. but keep it mind that (rather more frequently) the reverse also
happens .. 



> > least Alain B's terminfo took care of this problem.
> [...]
> > I then managed to get Vim and ELinks (again a 256-color capable version)
> > to use the 256 colors that my hardware was capable or (xterm configured
> > with 256 colors) by "saying so" in their respective config files.  And
> > both apps were kind enough to oblige.
> > 
> > mutt, OTOH only cares about what is specified in the terminfo entry
> 
> Okay, so to recap: you installed Alain B's terminfo description, and

(Continue reading)

headers

Alain Bench | 13 Sep 2006 15:55

Re: 256 colors

 On Wednesday, September 13, 2006 at 1:16:06 -0400, cga2000 wrote:

> I still have "defbce on" in my .screenrc but have not had time to test
> whether it is necessary when running with Alain's terminfo entry.

    "defbce on" is still necessary. Or rather, it has to be consistent:

 - Either "defbce on" and TERM=screen-256color-bce
 - Or set defbce off, and TERM=screen-256color

    The principle is that defbce changes one thing in the behaviour of
the Screen virtual terminal. And apps running inside need a terminfo
entry describing it accuratly.

    Note that in simple default case (outside of 256 colors), GNU Screen
is smart enough to autoexport TERM to "screen" or "screen-bce" depending
on this defbce setting.

    My advice: All the real terminals you use are able to do BCE, right?
Then pick the full BCE enabled setup: Should work optimally.

Bye!	Alain.
--

-- 
When you want to reply to a mailing list, please avoid doing so with
Lotus Notes 5. This lacks necessary references and breaks threads.

headers

Luis A. Florit | 12 Sep 2006 06:43

Re: 256 colors

CGA,

    Well, after many emails, you got mutt working with 256 colors!
But is quite difficult to follow your steps with so many emails...
Could you please make a small howto? I use a 256-color capable rxvt
that announces 'tput colors = 8'. Works great in Vim, but not in mutt.

    Thanks,

        Luis.

headers

Alain Bench | 12 Sep 2006 09:59

Re: 256 colors

Hello Luis,

 On Tuesday, September 12, 2006 at 1:43:54 -0300, Luis A. Florit wrote:

> I use a 256-color capable rxvt that announces 'tput colors = 8'.

    Configure your Rxvt so it auto-exports an appropriate TERM value:

| $ TERM=rxvt  tput colors
| 8
|
| $ TERM=rxvt-256color  tput colors
| 256

Bye!	Alain.
--

-- 
A "Reply-To:" header field pointing to the same email address
as the "From:" is uselessly redundant: A loss of space.

headers

Luis A. Florit | 15 Sep 2006 06:45

Re: 256 colors

Hi Alain,

* El 12/09/06 a las  9:59, Alain Bench chamullaba:

> Hello Luis,
>
>  On Tuesday, September 12, 2006 at 1:43:54 -0300, Luis A. Florit wrote:
>
> > I use a 256-color capable rxvt that announces 'tput colors = 8'.
>
> Configure your Rxvt so it auto-exports an appropriate TERM value:
>
> | $ TERM=rxvt  tput colors
> | 8
> |
> | $ TERM=rxvt-256color  tput colors
> | 256

I got errors:

    setenv TERM rxvt-256color
    tcsh: No entry for terminal type "rxvt-256color"
    tcsh: using dumb terminal settings.

Another try:

    $ TERM=rxvt-256color
    $ tput colors
    tput: unknown terminal "rxvt-256color"

(Continue reading)

headers

Alain Bench | 15 Sep 2006 18:35

Re: 256 colors

 On Friday, September 15, 2006 at 1:45:36 -0300, Luis A. Florit wrote:

>| tput: unknown terminal "rxvt-256color"

    Upgrade your terminfo database. This entry is quite recent, from
terminfo changelog:

| # 2006-04-22
| #	* add xterm+256color building block -TD
| #	* add gnome-256color, putty-256color, rxvt-256color -TD

    ...which means even latest ncurses 5.5 release doesn't provide it.

Bye!	Alain.
--

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

headers

cga2000 | 15 Sep 2006 08:24

Re: 256 colors

On Fri, Sep 15, 2006 at 12:45:36AM EDT, Luis A. Florit wrote:
> Hi Alain,
> 
> * El 12/09/06 a las  9:59, Alain Bench chamullaba:
> 
> > Hello Luis,
> >
> >  On Tuesday, September 12, 2006 at 1:43:54 -0300, Luis A. Florit wrote:
> >

[..]

> So, some terminfo is missing... But my rxvt works very well
> with vim and 256 colors.

I don't use rxvt but the Vim help may help understand why:

:help xterm16-256cterm

Thanks

cga

headers

Luis A. Florit | 18 Sep 2006 02:11

Re: 256 colors

* El 15/09/06 a las  2:24, cga2000 chamullaba:

> > So, some terminfo is missing... But my rxvt works very well
> > with vim and 256 colors.
>
> I don't use rxvt but the Vim help may help understand why:
>
> :help xterm16-256cterm

Sorry, I don't have that help tag in Vim. I use last Vim 7.0.

    Thanks,

        Luis.

headers

cga2000 | 18 Sep 2006 10:10

Re: 256 colors

On Sun, Sep 17, 2006 at 08:11:34PM EDT, Luis A. Florit wrote:
> * El 15/09/06 a las  2:24, cga2000 chamullaba:
> 
> > > So, some terminfo is missing... But my rxvt works very well
> > > with vim and 256 colors.
> >
> > I don't use rxvt but the Vim help may help understand why:
> >
> > :help xterm16-256cterm
> 
> Sorry, I don't have that help tag in Vim. I use last Vim 7.0.

Turns out this help file is part of the xterm16.vim plugin. 

http://www.vim.org

Thanks

cga

headers

Aaron Griffin | 12 Sep 2006 20:41

Re: 256 colors

On 9/12/06, Alain Bench <veronatif <at> free.fr> wrote:
>  On Tuesday, September 12, 2006 at 1:43:54 -0300, Luis A. Florit wrote:
> > I use a 256-color capable rxvt that announces 'tput colors = 8'.
>     Configure your Rxvt so it auto-exports an appropriate TERM value:

Or use something like this with tic:
http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/system/screen/screen-256color.ti?rev=HEAD&content-type=text/vnd.viewcvs-markup

Which was taken from the screen ML at some point.

headers

Alain Bench | 13 Sep 2006 03:35

Re: 256 colors

Hello Aaron,

 On Tuesday, September 12, 2006 at 13:41:47 -0500, Aaron Griffin wrote:

>> On Tuesday, September 12, 2006 at 1:43:54 -0300, Luis A. Florit wrote:
>>> I use a 256-color capable rxvt
> use something like this with tic: [screen-256color.ti]

    This is the entry posted by Nikolai Weibull on screen-users. It is a
good entry, but suffers from having been based on a rather old screen
one. The entry I posted here is slightly richer: Optimized color
commands, sgr, mouse support, bindable <BackTab>, and some such. Better
used with up-to-date terminfo, though: Its natural place is indeed
inside the official database.

    Also note that's probably not a solution for Luis: He asked about
Rxvt, and never talked about GNU Screen.

Bye!	Alain.
--

-- 
When you want to reply to a mailing list, please avoid doing so from a
digest. This often builds incorrect references and breaks threads.

headers

Aaron Griffin | 13 Sep 2006 16:56

Re: 256 colors

On 9/12/06, Alain Bench <veronatif <at> free.fr> wrote:
>     This is the entry posted by Nikolai Weibull on screen-users. It is a
> good entry, but suffers from having been based on a rather old screen
> one. The entry I posted here is slightly richer: Optimized color
> commands, sgr, mouse support, bindable <BackTab>, and some such. Better
> used with up-to-date terminfo, though: Its natural place is indeed
> inside the official database.

On an offtopic note, it's kind of hard to sift through this mailing,
let alone understand all the crazy terminfo stuff - could you provide
me with a concise terminfo entry for that you actually use, I'd like
to update the one linked above.

headers

cga2000 | 14 Sep 2006 00:20

Re: 256 colors

On Wed, Sep 13, 2006 at 10:56:29AM EDT, Aaron Griffin wrote:
> On 9/12/06, Alain Bench <veronatif <at> free.fr> wrote:
> >    This is the entry posted by Nikolai Weibull on screen-users. It is a
> >good entry, but suffers from having been based on a rather old screen
> >one. The entry I posted here is slightly richer: Optimized color
> >commands, sgr, mouse support, bindable <BackTab>, and some such. Better
> >used with up-to-date terminfo, though: Its natural place is indeed
> >inside the official database.
> 
> On an offtopic note, it's kind of hard to sift through this mailing,
> let alone understand all the crazy terminfo stuff - could you provide
> me with a concise terminfo entry for that you actually use, I'd like
> to update the one linked above.

If I understand rightly it's just a matter of following Alain's
recommendations .. create his screen-256color-bce and then infocmp it
back to a file.  Problem I see is that I'm not sure Alain's entry will
function 100% when the underlying terminal is not xterm (urxvt ..
pterm/putty .. Konsole/gnome-terminal if they have 256 color versions ..
etc.)

I do agree that folks googling for answers ending up with this thread
will find it rather confusing.  

Thanks

cga

headers

Rado S | 12 Sep 2006 17:06

Re: 256 colors

=- Luis A. Florit wrote on Tue 12.Sep'06 at  1:43:54 -0300 -=

> CGA,
> 
>     Well, after many emails, you got mutt working with 256 colors!
> But is quite difficult to follow your steps with so many
> emails... Could you please make a small howto? I use a 256-color
> capable rxvt that announces 'tput colors = 8'. Works great in
> Vim, but not in mutt.

Heh, cga, while you're at it, put it up as UserStory/MoreColors.
And remember to add ideas to UserGuide, too (see my other post. :)

--

-- 
© Rado S. -- You must provide YOUR effort for your goal!
Even if it seems insignificant, in fact EVERY effort counts
for a shared task, at least to show your deserving attitude.

headers

Kyle Wheeler | 25 Aug 2006 15:48

Re: 256 colors


On Thursday, August 24 at 05:03 PM, quoth cga2000:
>How can I have mutt display the 256 colors my xterm is capable of..?

I've never tried it, but this is what I would do:

Step 1: Make sure the $TERM variable points to a termcap description 
that describes the terminal as capable of that many colors.

Step 2: Get a version of ncurses/slang that supports that many colors.

Step 3: Recompile mutt.

I think it's that second step that's the hard one, but I'm not sure.

~Kyle
--

-- 
I have learned to be less confident in the conclusions of human 
reason, and give more credit to the honesty of contrary opinions.
                        -- Thomas Jefferson to Edward Livingston, 1824