Not so - the bullet and period are distinct: the period is at the bottom of the character, the bullet is in the centre.
I agree that for the Linux console, it is acceptable to expect people to amend their pref files if they wish to use ACS graphics. For me it's well worth doing so in order to have solid walls - others may wish to use -a and play with #s for walls.
I don't think a global replace of ACS_BULLET with a period is a good idea. It does look subtly different.
-
Me too.
I'm inclined to think that playing on the linux console is probably not very common now, and maybe you could count on those that do to also be able to handle changing their floor character with a pref file. At least, I was inclined to think that, until I went and checked on a gnome terminal and found bullet and period indistinguishable. So I think this post is a complete waste of everyone's time. Situation normal.I'm going to open a ticket about this. I think the correct resolution is just to always use period, unless there is a terminal for which period is a bad choice, in which case maybe "interact with graphics" or -a are the options.Leave a comment:
-
I can confirm this behavior on the linux console using ACS graphics.
The floors are currently using ACS_BULLET rather than period when in ACS graphics mode. I'm not sure if there are platforms where this is a significant improvement. It sounds like on the linux console, the ACS_BULLET character isn't a very good one to use.
Unfortunately, I think the fix for this is either changing the "floor" character angband uses back to period (either on a global basis, or in your pref) or using -a to turn off ACS graphics.
I'm going to open a ticket about this. I think the correct resolution is just to always use period, unless there is a terminal for which period is a bad choice, in which case maybe "interact with graphics" or -a are the options.Leave a comment:
-
Almost: here are my results using angband -mgcu -- -g ...
When I use PuTTY, the walls and floors use the correct ACS characters (solid block and centred dot respectively).
When I use a terminal in GNOME, again both walls and floors are correct.
When I use a linux console, either natively or via direct ssh (not PuTTY) the walls are correct but the floors are big ugly white squares (a very very big dot). I tried using the terminfo entry you sent me (by using TERM=xterm before invoking angband), and it got worse: the walls became the letter a, and the floors became tildes. Weird that it works for you and not for me.
Any idea what could be causing this?Leave a comment:
-
-
-
I already responded on IRC, but I will also put it here for posterity. Curses programs use your $TERM environment variable to figure out which capabilities your terminal has. They do this by looking up the terminfo or termcap entry that your system provides for this type. You can read this via "infocmp." For example:
There are two ways to fix this. The first is to specify a "better" TERM variable on the command-line. For instance "TERM=xterm angband -mgcu" This works well when your terminal emulator is confused, or your system hardcodes the TERM to something dumb. Sometimes color problems can be fixed by using "xterm-color" instead of "xterm". EDIT: for experimentation, here are a bunch of terminal types you can try out just to see what happens: ansi, vt100, vt102, vt220, rxvt, dumb, xterm, xterm-color, xterm-256color, screen.Code:joe@prompt$ infocmp dumb # Reconstructed via infocmp from file: /etc/terminfo/d/dumb dumb|80-column dumb tty, am, cols#80, bel=^G, cr=^M, cud1=^J, ind=^J,
The second way is by creating, or finding, a "better" terminfo entry to use. You can find them online or get them from other systems where things work better. This is kind of annoying, but if your distro gives you bad terminfo entries, it's the only way. You can then compile these with "tic FILE" which will create a local terminfo DB at "$HOME/.terminfo"
Whew! Hope that helps someone out.Leave a comment:
-
I shall be forever grateful - it is well beyond my coding ability. I'll happily test patches against any svn revision you care to name.Thank you. Next time I find myself with borked ASCII (by which I mean evil #s for walls instead of nice solid blocks) I'll run this and report back. Much as I appreciate the sense of your -a and -g options, playing with #s for walls is a total no-go for me. I would rather pull out my toenails.I'm attaching a pretty useful C program to inspect what curses believes about your terminal. You can compile it with "gcc -lncurses -o tty-colors tty-colors.c"
EDIT: Ok, I just tried this. I found a setup via PuTTY into my Debian-Sid box which gave me #s and no solid blocks available via "Interact with visuals" (which is on the main game options menu in 3.0.9b and is via the feature knowledge menu in 3.1.1). The program simply says:
... which is fine, but *why* do I have no ACS characters? When I log into that machine directly (not via ssh), the output is slightly different:Code:I am sorry, your terminal does not have the dim string in the capabilities I am sorry, your terminal does not have the init color string in the capabilities I am sorry, your terminal does not have the color names string in the capabilities I am sorry, your terminal does not have ACS characters in the capabilities Terminal: xterm You've got 8 colours You've got 64 pairs of colors possible To set foreground: ^[[3%p1%dm To set background: ^[[4%p1%dm To reset colours : ^[[39;49m To standout : ^[[7m To bold : ^[[1m To reverse : ^[[7m To blinking : ^[[5m To exit standout : ^[[27m To exit attribute: ^[[0m To original pairs: ^[[39;49m
... so what is determining the capabilities of these terminal environments, and how do I affect the provision of ACS characters?Code:I am sorry, your terminal does not have the color names string in the capabilities I am sorry, your terminal does not have ACS characters in the capabilities Terminal: linux You've got 8 colours You've got 64 pairs of colors possible To set foreground: ^[[3%p1%dm To set background: ^[[4%p1%dm To reset colours : ^[[39;49m To standout : ^[[7m To bold : ^[[1m To dim : ^[[2m To reverse : ^[[7m To blinking : ^[[5m To exit standout : ^[[27m To exit attribute: ^[[0m To init color : ^[]P%p1%x%p2%{256}%*%{1000}%/%02x%p3%{256}%*%{1000}%/%02x%p4%{256}%*%{1000}%/%02x To original pairs: ^[[39;49mLast edited by Magnate; August 17, 2009, 22:34.Leave a comment:
-
Somehow I managed to clobber that code before committing--I had something basically identical which I thought I checked in.
Anyway, thanks for catching that; it's fixed in HEAD now.
Do you have any idea why the graphics started working for you? Did you change any settings?Leave a comment:
-
I added these lines to my code:
It works fine.Code:else if (prefix(argv[i], "-a")) use_alt_charset = 0;
Leave a comment:
-
-
That's really strange. Does the help menu list -a and -g as new options?
Did you make clean? Are you running r1628? I have no explanation for the behavior you see, although I'm glad the wall tiles are working for you now. I tested -a and -g on a number of terminals and both work fine for me.
Later today I will try running Angband in an xterm with your termcap file and see what happens.Leave a comment:
-
-
Code:# Reconstructed via infocmp from file: /usr/share/terminfo/x/xterm xterm|xterm terminal emulator (X Window System), 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=\E[1;2P, kf14=\E[1;2Q, kf15=\E[1;2R, kf16=\E[1;2S, 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=\E[1;5P, kf26=\E[1;5Q, kf27=\E[1;5R, kf28=\E[1;5S, 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=\E[1;6P, kf38=\E[1;6Q, kf39=\E[1;6R, kf4=\EOS, kf40=\E[1;6S, 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=\E[1;3P, kf5=\E[15~, kf50=\E[1;3Q, kf51=\E[1;3R, kf52=\E[1;3S, 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=\E[1;4P, kf62=\E[1;4Q, kf63=\E[1;4R, kf7=\E[18~, kf8=\E[19~, kf9=\E[20~, khome=\EOH, kich1=\E[2~, kind=\E[1;2B, kmous=\E[M, knp=\E[6~, kpp=\E[5~, kri=\E[1;2A, 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>, rmm=\E[?1034l, 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=%?%p9%t\E(0%e\E(B%;\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m, sgr0=\E(B\E[m, smacs=\E(0, smam=\E[?7h, smcup=\E[?1049h, smir=\E[4h, smkx=\E[?1h\E=, smm=\E[?1034h, 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,No.Are you running from within screen? Over SSH?
I'll try out the new option that you added.Leave a comment:
Leave a comment: