From: Seiichi S. <ss...@sh...> - 2004-10-17 09:58:02
|
On Sun, Oct 17, 2004 at 05:06:33PM +0900, Minami Hirokazu wrote: > Seiichi SATO wrote: > > On Sun, Oct 17, 2004 at 04:26:41AM +0200, > > Nuno Alexandre wrote: > > > > Im still having issues with the colors, > > > take alook at this snapshot: > > > <URL: http://ikaro.homepage.dk/2004-10-17-01-17_1600x1200.png> > > > The 'ugly' one is mlterm. > > > > > > Why are the colors in mutt completly different, than in the two aterms? > > > > If your mutt was compiled with slang. that is a known issue. > > > > <http://www.sh.rim.or.jp/~ssato/mlterm/debian_bts_267294.png> > > > > I am working to solve this problem, but i don't know why it > > occurs. > > It seems to be a slang's problem that do not work well > on a terminal which lacks a feature called "bce". > > Though mlterm can mimic the feature to some extent, > it will run a bit slowly and consume more memory in that case. > So if you are using mlterm with TERM=mlterm, > its bce emulation is disabled by default. > > To make mlterm behave as a bce terminal, the simplest way may be > executing mlterm with TERM=xterm. What happens if you do > mlterm -y=xterm > and run mutt on it? Unfortunately, i got the same result on mlterm -y=xterm. It seems not to be bce problem. I found out what was doing for setting fg/bg colors in slang. slang's changelog said: 4. If a color called `default' is specified, the escape sequence to set the default color will be sent. Be careful, not all terminals support this feature. If your terminal supports it, e.g., rxvt, then using setenv COLORFGBG default is a good choice. I tried to run mutt in mlterm as below. $ COLORFGBG=default mutt so it works:) Nuno, To avoid the problem, set COLORFGBG environment variable. Minami-san, rxvt seems to set COLORFGBG by default. (main.c) I'll add this feature to mlterm. # COLORFGBG is rxvt's original extention??? -- Seiichi |