Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

3.1.2 colour bug

0 views
Skip to first unread message

Matthew Vernon

unread,
Jan 27, 2010, 10:39:23 AM1/27/10
to
Hi,

The Metallic green centipede isn't appearing as green for me (console,
linux, 3.1.2), but rather as brown (same colour as a Jackal, for
example); FWIW, the village idiot does appear in green.

The only configuration I did was to move font-gcu.prf out of the way
(because I like #s for walls).

Cheers,

Matthew

--
Rapun.sel - outermost outpost of the Pick Empire
http://www.pick.ucam.org

Matthew Vernon

unread,
Jan 27, 2010, 10:42:42 AM1/27/10
to
Matthew Vernon <mat...@debian.org> writes:

> Hi,
>
> The Metallic green centipede isn't appearing as green for me (console,
> linux, 3.1.2), but rather as brown (same colour as a Jackal, for
> example); FWIW, the village idiot does appear in green.

I also note that Dark and Gloopy green potitions appear brown
(although Chartreuse is correct).

Matthew Vernon

unread,
Jan 27, 2010, 6:16:51 PM1/27/10
to
Matthew Vernon <mat...@debian.org> writes:

> Matthew Vernon <mat...@debian.org> writes:
>
> > Hi,
> >
> > The Metallic green centipede isn't appearing as green for me (console,
> > linux, 3.1.2), but rather as brown (same colour as a Jackal, for
> > example); FWIW, the village idiot does appear in green.
>
> I also note that Dark and Gloopy green potitions appear brown
> (although Chartreuse is correct).

...and that Smeagol is also brown (that really threw me). What's wrong
with the colours?!?

Andi Sidwell

unread,
Jan 27, 2010, 6:26:58 PM1/27/10
to
On 2010-01-27 23:16, Matthew Vernon wrote:
> Matthew Vernon<mat...@debian.org> writes:
>
>> Matthew Vernon<mat...@debian.org> writes:
>>
>>> Hi,
>>>
>>> The Metallic green centipede isn't appearing as green for me (console,
>>> linux, 3.1.2), but rather as brown (same colour as a Jackal, for
>>> example); FWIW, the village idiot does appear in green.
>>
>> I also note that Dark and Gloopy green potitions appear brown
>> (although Chartreuse is correct).
>
> ...and that Smeagol is also brown (that really threw me). What's wrong
> with the colours?!?

I'm really not sure. What are you playing on and with which port?

Matthew Vernon

unread,
Jan 28, 2010, 2:48:05 AM1/28/10
to
Andi Sidwell <an...@takkaria.org> writes:

Linux rapun 2.6.18 #2 Sun Dec 21 22:14:50 GMT 2008 i686 GNU/Linux

built with:

$ ./configure --enable-x11 --prefix=/var/newangband --with-setgid=games --disa
ble-sdl-mixer

As noted earlier, I renamed font-gcu.prf (as that was suggested as a
way to make 3.1.x have #s for walls)

I play on a text console (i.e. not under X); playing on X gets the
colours right.

HTH,

Antoine

unread,
Jan 28, 2010, 4:31:10 AM1/28/10
to
On Jan 28, 12:16 pm, Matthew Vernon <matt...@debian.org> wrote:
> Matthew Vernon <matt...@debian.org> writes:

> > Matthew Vernon <matt...@debian.org> writes:
>
> > > Hi,
>
> > > The Metallic green centipede isn't appearing as green for me (console,
> > > linux, 3.1.2), but rather as brown (same colour as a Jackal, for
> > > example); FWIW, the village idiot does appear in green.
>
> > I also note that Dark and Gloopy green potitions appear brown
> > (although Chartreuse is correct).
>
> ...and that Smeagol is also brown (that really threw me). What's wrong
> with the colours?!?

Youve drunk a potion of Everything Looks Like Crap

A.

Matthew Vernon

unread,
Jan 28, 2010, 7:00:14 AM1/28/10
to
Andi Sidwell <an...@takkaria.org> writes:

> I'm really not sure. What are you playing on and with which port?

Further to this, I've had a look at the "interact with colours" menu,
and colour 5 is described as r=0x00 g=0x80 b=0x40 (which is the same
as that colour is in a 3.0.6 build I've got knocking around), whereas
it looks the same as Umber (r=0x80, g=0x40, b=0x00).

FWIW, colours 5,7,15-26 all look the same brown colour, despite the
interact with colours menu giving them different rgb values.

Matthew Vernon

unread,
Jan 28, 2010, 7:05:09 AM1/28/10
to
Andi Sidwell <an...@takkaria.org> writes:

> I'm really not sure. What are you playing on and with which port?

I also tried it on my work desktop

Linux b144-mcv1-mlt 2.6.20-2-macpro-amd64 #1 SMP Sun Jul 29 11:30:30 EDT 2007 x86_64 GNU/Linux

built with ./configure --enable-x11 --with-no-install --disable-sdl-mixer

...and again, running on a text console, I see the same bug.

Magnate

unread,
Feb 1, 2010, 6:34:05 AM2/1/10
to
"Matthew Vernon" <mat...@debian.org> wrote

> Andi Sidwell <an...@takkaria.org> writes:
>
>> I'm really not sure. What are you playing on and with which port?
>
> Further to this, I've had a look at the "interact with colours" menu,
> and colour 5 is described as r=0x00 g=0x80 b=0x40 (which is the same
> as that colour is in a 3.0.6 build I've got knocking around), whereas
> it looks the same as Umber (r=0x80, g=0x40, b=0x00).
>
> FWIW, colours 5,7,15-26 all look the same brown colour, despite the
> interact with colours menu giving them different rgb values.

Thanks for the bug report - I'll bring it to the attention of d_m, who is
fortunately a dab hand with both main-gcu and colours.

Glad it works ok under X

CC

Matthew Vernon

unread,
Feb 1, 2010, 7:19:44 AM2/1/10
to
"Magnate" <n...@receiving.here> writes:

Grand; I didn't relish trying to debug ncurses :) If you remember, a
prod as and when it's fixed so I can patch my install would be Very Nice.

Ta,

d_m

unread,
Feb 1, 2010, 10:38:55 AM2/1/10
to
Hi Matthew,

This is d_m... I have some more detailed questions about your color
issue:

1. What terminal emulator (or terminal) are you using? Linux console?
xterm? gnome-terminal? rxvt? aterm?
2. What is the value of $TERM? I would expect something like: xterm,
ansi, xterm-256color, xterm-color, rxvt, screen, linux
3. What is the output of infocmp?
4. If you try running with "other" TERM types, e.g. 'TERM=xterm
angband -mgcu' does it work? What happens for different ones?

5. FWIW, you don't need to move/delete font-gcu.prf to get # walls--if
you run "angband -mgcu -- -a" you will get them also. If you wouldn't
mind putting the file back, then try that and let me know what
happens?

6.It sounds to me like maybe you're using a bad $TERM/terminal
combination. Do other ncurses programs with color work in your setup
(e.g. vim, mutt, other *bands, etc)?

Matthew Vernon

unread,
Feb 1, 2010, 10:55:21 AM2/1/10
to
d_m <stark...@gmail.com> writes:

> Hi Matthew,
>
> This is d_m... I have some more detailed questions about your color
> issue:
>
> 1. What terminal emulator (or terminal) are you using? Linux console?
> xterm? gnome-terminal? rxvt? aterm?
> 2. What is the value of $TERM? I would expect something like: xterm,
> ansi, xterm-256color, xterm-color, rxvt, screen, linux
> 3. What is the output of infocmp?

I observe this problem with two different configurations; I'm only
really interested in getting the Linux console working (since that's
what I primarily use).

i) linux console:
1. [linux console]
2. linux
3.

# Reconstructed via infocmp from file: /lib/terminfo/l/linux
linux|linux console,
am, bce, ccc, eo, mir, msgr, xenl, xon,
colors#8, it#8, ncv#18, pairs#64,
acsc=+\020\,\021-\030.^Y0\333`\004a\261f\370g\361h\260i\316j\331k\277l\332m\300n\305o~p\304q\304r\304s_t\303u\264v\301w\302x\263y\363z\362{\343|\330}\234~\376,
bel=^G, blink=\E[5m, bold=\E[1m, civis=\E[?25l\E[?1c,
clear=\E[H\E[J, cnorm=\E[?25h\E[?0c, cr=^M,
csr=\E[%i%p1%d;%p2%dr, cub1=^H, cud1=^J, cuf1=\E[C,
cup=\E[%i%p1%d;%p2%dH, cuu1=\E[A, cvvis=\E[?25h\E[?8c,
dch=\E[%p1%dP, dch1=\E[P, dim=\E[2m, dl=\E[%p1%dM,
dl1=\E[M, ech=\E[%p1%dX, ed=\E[J, el=\E[K, el1=\E[1K,
flash=\E[?5h\E[?5l$<200/>, home=\E[H, hpa=\E[%i%p1%dG,
ht=^I, hts=\EH, ich=\E[%p1%d@, ich1=\E[@, il=\E[%p1%dL,
il1=\E[L, ind=^J,
initc=\E]P%p1%x%p2%{256}%*%{1000}%/%02x%p3%{256}%*%{1000}%/%02x%p4%{256}%*%{1000}%/%02x,
invis=\E[8m, kb2=\E[G, kbs=\177, kcbt=\E[Z, kcub1=\E[D,
kcud1=\E[B, kcuf1=\E[C, kcuu1=\E[A, kdch1=\E[3~,
kend=\E[4~, kf1=\E[[A, kf10=\E[21~, kf11=\E[23~,
kf12=\E[24~, kf13=\E[25~, kf14=\E[26~, kf15=\E[28~,
kf16=\E[29~, kf17=\E[31~, kf18=\E[32~, kf19=\E[33~,
kf2=\E[[B, kf20=\E[34~, kf3=\E[[C, kf4=\E[[D, kf5=\E[[E,
kf6=\E[17~, kf7=\E[18~, kf8=\E[19~, kf9=\E[20~,
khome=\E[1~, kich1=\E[2~, kmous=\E[M, knp=\E[6~, kpp=\E[5~,
kspd=^Z, nel=^M^J, oc=\E]R, op=\E[39;49m, rc=\E8, rev=\E[7m,
ri=\EM, rmacs=\E[10m, rmam=\E[?7l, rmir=\E[4l,
rmpch=\E[10m, rmso=\E[27m, rmul=\E[24m, rs1=\Ec\E]R,
sc=\E7, setab=\E[4%p1%dm, setaf=\E[3%p1%dm,
sgr=\E[0;10%?%p1%t;7%;%?%p2%t;4%;%?%p3%t;7%;%?%p4%t;5%;%?%p5%t;2%;%?%p6%t;1%;%?%p7%t;8%;%?%p9%t;11%;m,
sgr0=\E[0;10m, smacs=\E[11m, smam=\E[?7h, smir=\E[4h,
smpch=\E[11m, smso=\E[7m, smul=\E[4m, tbc=\E[3g,
u6=\E[%i%d;%dR, u7=\E[6n, u8=\E[?6c, u9=\E[c,
vpa=\E[%i%p1%dd,

ii) xterminal:
1) xterm
2) xterm
3) # Reconstructed via infocmp from file: /lib/terminfo/x/xterm
xterm|X11 terminal emulator,
am, bce, km, mc5i, mir, msgr, npc, xenl,
colors#8, cols#80, it#8, lines#24, pairs#64,
acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
bel=^G, blink=\E[5m, bold=\E[1m, cbt=\E[Z, civis=\E[?25l,
clear=\E[H\E[2J, cnorm=\E[?12l\E[?25h, cr=^M,
csr=\E[%i%p1%d;%p2%dr, cub=\E[%p1%dD, cub1=^H,
cud=\E[%p1%dB, cud1=^J, cuf=\E[%p1%dC, cuf1=\E[C,
cup=\E[%i%p1%d;%p2%dH, cuu=\E[%p1%dA, cuu1=\E[A,
cvvis=\E[?12;25h, dch=\E[%p1%dP, dch1=\E[P, dl=\E[%p1%dM,
dl1=\E[M, ech=\E[%p1%dX, ed=\E[J, el=\E[K, el1=\E[1K,
flash=\E[?5h$<100/>\E[?5l, home=\E[H, hpa=\E[%i%p1%dG,
ht=^I, hts=\EH, ich=\E[%p1%d@, il=\E[%p1%dL, il1=\E[L,
ind=^J, indn=\E[%p1%dS, invis=\E[8m,
is2=\E[!p\E[?3;4l\E[4l\E>, kDC=\E[3;2~, kEND=\E[1;2F,
kHOM=\E[1;2H, kIC=\E[2;2~, kLFT=\E[1;2D, kNXT=\E[6;2~,
kPRV=\E[5;2~, kRIT=\E[1;2C, kb2=\EOE, kbs=\177, kcbt=\E[Z,
kcub1=\EOD, kcud1=\EOB, kcuf1=\EOC, kcuu1=\EOA,
kdch1=\E[3~, kend=\EOF, kent=\EOM, kf1=\EOP, kf10=\E[21~,
kf11=\E[23~, kf12=\E[24~, kf13=\EO2P, kf14=\EO2Q,
kf15=\EO2R, kf16=\EO2S, kf17=\E[15;2~, kf18=\E[17;2~,
kf19=\E[18;2~, kf2=\EOQ, kf20=\E[19;2~, kf21=\E[20;2~,
kf22=\E[21;2~, kf23=\E[23;2~, kf24=\E[24;2~, kf25=\EO5P,
kf26=\EO5Q, kf27=\EO5R, kf28=\EO5S, kf29=\E[15;5~,
kf3=\EOR, kf30=\E[17;5~, kf31=\E[18;5~, kf32=\E[19;5~,
kf33=\E[20;5~, kf34=\E[21;5~, kf35=\E[23;5~,
kf36=\E[24;5~, kf37=\EO6P, kf38=\EO6Q, kf39=\EO6R,
kf4=\EOS, kf40=\EO6S, kf41=\E[15;6~, kf42=\E[17;6~,
kf43=\E[18;6~, kf44=\E[19;6~, kf45=\E[20;6~,
kf46=\E[21;6~, kf47=\E[23;6~, kf48=\E[24;6~, kf49=\EO3P,
kf5=\E[15~, kf50=\EO3Q, kf51=\EO3R, kf52=\EO3S,
kf53=\E[15;3~, kf54=\E[17;3~, kf55=\E[18;3~,
kf56=\E[19;3~, kf57=\E[20;3~, kf58=\E[21;3~,
kf59=\E[23;3~, kf6=\E[17~, kf60=\E[24;3~, kf61=\EO4P,
kf62=\EO4Q, kf63=\EO4R, kf7=\E[18~, kf8=\E[19~, kf9=\E[20~,
khome=\EOH, kich1=\E[2~, kmous=\E[M, knp=\E[6~, kpp=\E[5~,
mc0=\E[i, mc4=\E[4i, mc5=\E[5i, meml=\El, memu=\Em,
op=\E[39;49m, rc=\E8, rev=\E[7m, ri=\EM, rin=\E[%p1%dT,
rmacs=\E(B, rmam=\E[?7l, rmcup=\E[?1049l, rmir=\E[4l,
rmkx=\E[?1l\E>, rmso=\E[27m, rmul=\E[24m, rs1=\Ec,
rs2=\E[!p\E[?3;4l\E[4l\E>, sc=\E7, setab=\E[4%p1%dm,
setaf=\E[3%p1%dm,
setb=\E[4%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,
setf=\E[3%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,
sgr=\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m%?%p9%t\E(0%e\E(B%;,
sgr0=\E[m\E(B, smacs=\E(0, smam=\E[?7h, smcup=\E[?1049h,
smir=\E[4h, smkx=\E[?1h\E=, smso=\E[7m, smul=\E[4m,
tbc=\E[3g, u6=\E[%i%d;%dR, u7=\E[6n, u8=\E[?1;2c, u9=\E[c,
vpa=\E[%i%p1%dd,

> 4. If you try running with "other" TERM types, e.g. 'TERM=xterm
> angband -mgcu' does it work? What happens for different ones?

in xterm, TERM=xterm-256color makes the colors seem correct. It does
Bad Things on the console if I try that (lots of flashing stuff).



> 5. FWIW, you don't need to move/delete font-gcu.prf to get # walls--if
> you run "angband -mgcu -- -a" you will get them also. If you wouldn't
> mind putting the file back, then try that and let me know what
> happens?

I get # walls, but the colours are still broken.



> 6.It sounds to me like maybe you're using a bad $TERM/terminal
> combination. Do other ncurses programs with color work in your setup
> (e.g. vim, mutt, other *bands, etc)?

Yep; ever single ncurses program I can lay my hands on works,
including every version of angband up to and including 3.1.1.1626;
it's only 3.1.2 that has this bug.

HTH,

d_m

unread,
Feb 1, 2010, 11:46:48 AM2/1/10
to
Wait, I can totally reproduce this under the linux terminal. I'll let
you know as soon as I have a fix.

Thanks for catching this!

Wally the Grey

unread,
Feb 1, 2010, 11:47:39 AM2/1/10
to
Matthew Vernon wrote:
> Grand; I didn't relish trying to debug ncurses :) If you remember, a
> prod as and when it's fixed so I can patch my install would be Very Nice.

This is very odd. "If you remember" would ordinarily be followed by a
recapping of some prior piece of information, but here it seems to be
followed by a novel suggestion of something to do in the future.

Matthew Vernon

unread,
Feb 1, 2010, 11:57:27 AM2/1/10
to

Maybe a re-phrasing would make my intent clear: "As and when it's
fixed, if you happen to remember this request, could you let me know"?

The Wanderer

unread,
Feb 1, 2010, 12:26:23 PM2/1/10
to

It didn't seem odd to me; it's plainly a compaction of "if you remember
(to provide one by that point), a prod" et cetera.

--
The Wanderer

Warning: Simply because I argue an issue does not mean I agree with any
side of it.

Secrecy is the beginning of tyranny.

d_m

unread,
Feb 1, 2010, 12:57:19 PM2/1/10
to
OK, so it ended up not even being that complicated--it was a typo that
only showed itself if you played with 16 colors.

I just committed a fix to HEAD. If you have a checkout of the source
you should be able to update, rebuild and have the problem fixed.
Otherwise you'll need to wait for the next nightly build. Please let
me know when you notice it's fixed (when I did this it fixed it for
me).

Matthew Vernon

unread,
Feb 1, 2010, 1:36:44 PM2/1/10
to
d_m <stark...@gmail.com> writes:

I've applied your patch to my 3.1.2 tree, and I now have 14 distinct
colours (which I assume is the desired effect on console).

Cheers,

d_m

unread,
Feb 1, 2010, 2:12:23 PM2/1/10
to
> I've applied your patch to my 3.1.2 tree, and I now have 14 distinct
> colours (which I assume is the desired effect on console).

Correct! Thanks for verifying this. I'm going to close the open ticket
about this.

0 new messages