Termcap broken?
Hi... I'm getting the error Terminal must backspace. when trying to run Slash'EM (a Nethack-derived game). I'm not sure what's gotten broken, but if I copy over the termcap and termcap.db from a 4.6-STABLE machine (of mid-August), it works again. Any suggestions on how to fix this? My TERM environment variable is set to xterm-color right now, but changing it to xterm doesn't seem to make a difference. thanks -Adam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Termcap broken?
Adam Kranzel wrote: I'm getting the error Terminal must backspace. when trying to run Slash'EM (a Nethack-derived game). I'm not sure what's gotten broken, but if I copy over the termcap and termcap.db from a 4.6-STABLE machine (of mid-August), it works again. Any suggestions on how to fix this? My TERM environment variable is set to xterm-color right now, but changing it to xterm doesn't seem to make a difference. The best thing to do would be to look at the source code for the program, and see what is making it spit out the message, and figure out how to correct that. One common issue in this are is terminals whose left arrow emits ASCII BS (^H) instead of having a seperate escape sequence (e.g. Televideo, Wyse, Hazeltine terminals). Another is people who define the PC console backspace key to send ASCII DEL instead of ASCII BS. The last is when there is no such thing as a backspace that is non-destructive (e.g. some terminals do not allow you to use ASCII BS sent to the terminal to move the curosr left, without actually erasing the character under the cursor). Like I said: look at the code, and find out what entries make it emit the error message that you are seeing. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
÷ Sat, 31.08.2002, × 02:04, Jens Schweikhardt ÎÁÐÉÓÁÌ: On Thu, Aug 29, 2002 at 05:03:17PM +0400, Vladimir B. Grebenschikov wrote: # ? Wed, 28.08.2002, ? 23:46, Bruce A. Mah ???: # If memory serves me right, Jens Schweikhardt wrote: # # # Do you have time to commit mention of it to UPDATING? If so, please # # draw Bruce Mah's attention to the delta so that he can steal your text # # for use in the release notes. If not, I'll get around to it eventually. # # :-) # # I just added a note to src/UPDATING. Bruce, are you listening # for the release notes? # # 20020827: # Our /etc/termcap now has all the entries from the XFree86 xterm # almost unchanged. This means xterm now supports color by default. # If you used TERM=xterm-color in the past you now should use # TERM=xterm. (xterm-color will lead to benign warnings). # # # After this update, xterm-color produce warnings: # vbook:/home/vova 129_ mc # TERMCAP, line 0, terminal 'xterm-color': enter_alt_charset_mode but no # acs_chars # TERMCAP, line 0, terminal 'xterm-color': exit_alt_charset_mode but no # acs_chars # # and midnight commander shows all with -, +, | instead of # pesudo-graphics. It seems this is the price we pay for alignment with what XFree86 ships. I see # Ok I have tried setenv TERM xterm, midnight commander now black and # white, where I have mistaken ? I just installed the misc/mc package from 4.6 and midc is fully colored under xterm, rxvt and the console. Do you have a stale termcap.db? Does midc use/read some config file that says no color? No, after restarting xterm all works fine, my fault sorry. Thanx anyway. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) -- Vladimir B. Grebenschikov [EMAIL PROTECTED], SWsoft, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
On Thu, Aug 29, 2002 at 01:46:05PM -0700, David O'Brien wrote: This is *totally* UNTRUE: /usr/local/bin//mutt: libslang.so = /usr/local/lib/libslang.so (0x280e5000) libm.so.2 = /usr/lib/libm.so.2 (0x28148000) libssl.so.2 = /usr/lib/libssl.so.2 (0x28167000) libcrypto.so.2 = /usr/lib/libcrypto.so.2 (0x28199000) libxpg4.so.3 = /usr/lib/libxpg4.so.3 (0x28263000) libintl.so.2 = /usr/local/lib/libintl.so.2 (0x28265000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x2826c000) libncurses.so.5 = /usr/lib/libncurses.so.5 (0x2834) libc.so.5 = /usr/lib/libc.so.5 (0x28382000) note the use of libslang. TERM=xterm and not having COLORTERM set, mutt will not use colors. TERM=xterm and COLORTERM=yes, mutt will use colors. TERM=xterm-color (COLORTERM set or not), mutt will use colors. Speaking of mutt. The end keys on my keyboard no longer work within mutt and xterm. The work just fine with some other programs and work fine still within a console. Just no longer within an xterm. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
... # # and midnight commander shows all with -, +, | instead of # # pesudo-graphics. # # It seems this is the price we pay for alignment with what XFree86 ships. # # I see Wait, maybe I was too fast and there is a solution. Looking at the xterm FAQ, http://dickey.his.com/xterm/xterm.faq.html My terminal doesn't show box characters Xterm displays the 7-bit ASCII and VT100 graphic characters (including box corners) using specially arranged fixed-pitch fonts. The first 32 glyph positions (which would correspond to nonprinting control characters) are used to hold the VT100 graphic characters. Some fonts that otherwise look fine (such as courier) do not have glyphs defined for these positions. So they display as blanks. Use xfd to display the font. XFree86 xterm can form its own line-drawing characters (see patch 90, for example). It does not draw all of the graphic characters, only those that may be done with straight lines. But those are the most used, making most of the fixed-pitch fonts useful for xterm. You may also have a problem with the terminfo description. As distributed, the X11R6 terminfo for xterm does not have the acsc string defined, so most implementations of curses do not try to use the alternate character set. Finally, some people confuse the VT100 graphic characters with the VT220 support for DEC technical character set. These are distinct (7-bit) character sets. Xterm currently does not support this. I found that it is really dependent on the font. I use some IBM font from an AIX system (Rom14) by default, which has no box characters and thus displays blanks instead. If I use e.g. $ xterm -fn fixed -e midc I have all the box characters and midc looks good. Use $ xfd -fn whateverfont and look at the first 32 characters. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
On Wed, Aug 28, 2002 at 09:41:05PM +0200, Jens Schweikhardt wrote: 20020827: Our /etc/termcap now has all the entries from the XFree86 xterm almost unchanged. This means xterm now supports color by default. If you used TERM=xterm-color in the past you now should use TERM=xterm. (xterm-color will lead to benign warnings). This is unacceptable -- you are breaking cross-platform (even -stable to -current) logins. TERM=xterm-color should work just as well and w/o warnings it did before your commit. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
On Wed, Aug 28, 2002 at 07:06:40PM +0200, Jens Schweikhardt wrote: # Mutt shows this when I start vi as my editor or run fetchmail: # # TERMCAP, line 0, terminal 'xterm-color': enter_alt_charset_mode but no acs_chars # # My centericq window ends up using pipe signs (|), minus signs (-) and # plus signs (+) to draw boxes. . Please use plain TERM=xterm which now has color support. If any problems remain, please let me know. Are you saying to try TERM=xterm as a test, or that TERM=xterm-color is not longer supported? If the second, that is unacceptable. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
On Wed, Aug 28, 2002 at 02:06:54PM -0500, Dan Nelson wrote: In the last episode (Aug 28), Jens Schweikhardt said: On Wed, Aug 28, 2002 at 07:35:32PM +0200, Sheldon Hearn wrote: # On (2002/08/28 19:04), Jens Schweikhardt wrote: # Yes, use plain TERM=xterm. It's got color now as it should. I'm # thinking of removing xterm-color if I can't resolve the # enter_alt_charset_mode stuff. Let me know if TERM=xterm does not # work as expected in mutt et al. I'll post a minor HEADS UP to # current@. # # Doesn't work for centericq or mutt. Are you sure? I use mutt too (in an rxvt), and TERM=xterm works wonderfully with colors. Hang on, will test mutt in plain xterm... yes, works there too. Older versions of the mutt port used the slang terminal library, which had (has?) a bug that assumed that all xterms supported color. It didn't matter what your termcap says. This is *totally* UNTRUE: /usr/local/bin//mutt: libslang.so = /usr/local/lib/libslang.so (0x280e5000) libm.so.2 = /usr/lib/libm.so.2 (0x28148000) libssl.so.2 = /usr/lib/libssl.so.2 (0x28167000) libcrypto.so.2 = /usr/lib/libcrypto.so.2 (0x28199000) libxpg4.so.3 = /usr/lib/libxpg4.so.3 (0x28263000) libintl.so.2 = /usr/local/lib/libintl.so.2 (0x28265000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x2826c000) libncurses.so.5 = /usr/lib/libncurses.so.5 (0x2834) libc.so.5 = /usr/lib/libc.so.5 (0x28382000) note the use of libslang. TERM=xterm and not having COLORTERM set, mutt will not use colors. TERM=xterm and COLORTERM=yes, mutt will use colors. TERM=xterm-color (COLORTERM set or not), mutt will use colors. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
On Thu, Aug 29, 2002 at 05:03:17PM +0400, Vladimir B. Grebenschikov wrote: # ? Wed, 28.08.2002, ? 23:46, Bruce A. Mah ???: # If memory serves me right, Jens Schweikhardt wrote: # # # Do you have time to commit mention of it to UPDATING? If so, please # # draw Bruce Mah's attention to the delta so that he can steal your text # # for use in the release notes. If not, I'll get around to it eventually. # # :-) # # I just added a note to src/UPDATING. Bruce, are you listening # for the release notes? # # 20020827: # Our /etc/termcap now has all the entries from the XFree86 xterm # almost unchanged. This means xterm now supports color by default. # If you used TERM=xterm-color in the past you now should use # TERM=xterm. (xterm-color will lead to benign warnings). # # # After this update, xterm-color produce warnings: # vbook:/home/vova 129_ mc # TERMCAP, line 0, terminal 'xterm-color': enter_alt_charset_mode but no # acs_chars # TERMCAP, line 0, terminal 'xterm-color': exit_alt_charset_mode but no # acs_chars # # and midnight commander shows all with -, +, | instead of # pesudo-graphics. It seems this is the price we pay for alignment with what XFree86 ships. # Ok I have tried setenv TERM xterm, midnight commander now black and # white, where I have mistaken ? I just installed the misc/mc package from 4.6 and midc is fully colored under xterm, rxvt and the console. Do you have a stale termcap.db? Does midc use/read some config file that says no color? Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
On Sat, Aug 31, 2002 at 00:04:44 +0200, Jens Schweikhardt wrote: # and midnight commander shows all with -, +, | instead of # pesudo-graphics. It seems this is the price we pay for alignment with what XFree86 ships. We don't need to pay, if entries will be _really_ corrected instead of _blindly_ updated. If you don't have experience to correct new entry afterwards to satisfy requirements, better back out this commit. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
On Sat, Aug 31, 2002 at 00:04:44 +0200, Jens Schweikhardt wrote: # and midnight commander shows all with -, +, | instead of # pesudo-graphics. It seems this is the price we pay for alignment with what XFree86 ships. We don't need to pay, if entries will be _really_ corrected instead of _blindly_ updated. IMHO, it has been corrected, and was incorrect before. FWIW, this would also appear to be the opinion of the current maintainer of 'xterm' for XFree86. Ache, have you read bin/41143? Regards, AS msg42324/pgp0.pgp Description: PGP signature
Re: CURRENT's termcap broken
On Fri, Aug 30, 2002 at 21:47:16 -0400, Andy Sparrow wrote: On Sat, Aug 31, 2002 at 00:04:44 +0200, Jens Schweikhardt wrote: # and midnight commander shows all with -, +, | instead of # pesudo-graphics. It seems this is the price we pay for alignment with what XFree86 ships. We don't need to pay, if entries will be _really_ corrected instead of _blindly_ updated. IMHO, it has been corrected, and was incorrect before. I mean, corrected for ACS characters (pseudo-graphics), which are correct before. Read complains above. Ache, have you read bin/41143? To fix what you mean, just moving 'xterm-color' entry additional color capabilities directly to 'xterm' entry and making 'xterm-color' as alias to 'xterm' will be enough to fix PR. -- Andrey A. Chernov http://ache.pp.ru/ msg42325/pgp0.pgp Description: PGP signature
Re: CURRENT's termcap broken
IMHO, it has been corrected, and was incorrect before. I mean, corrected for ACS characters (pseudo-graphics), which are correct before. Read complains above. I believe that these are fixed by not using an incorrect termtype (e.g. 'xterm-color', which refers to another terminal type altogether). Ache, have you read bin/41143? To fix what you mean, just moving 'xterm-color' entry additional color capabilities directly to 'xterm' entry and making 'xterm-color' as alias to 'xterm' will be enough to fix PR. Hmmm. Except that 'xterm-color' is widely used as a cap for an older (and incompatible) termtype, as stated in the PR. And the author of xterm has widely criticised FreeBSD's incorrect handling of other attributes. To the point where he has documented the brokeness in his FAQ, and specifically advises to use the termcap supplied with 'xterm'. Again, as stated in the PR. Specifically: http://dickey.his.com/xterm/xterm.faq.html#xterm_terminfo Regards, AS msg42326/pgp0.pgp Description: PGP signature
Re: CURRENT's termcap broken
On Fri, Aug 30, 2002 at 22:12:33 -0400, Andy Sparrow wrote: And the author of xterm has widely criticised FreeBSD's incorrect handling of other attributes. To the point where he has documented the brokeness in his FAQ, and specifically advises to use the termcap supplied with 'xterm'. Again, as stated in the PR. Specifically: http://dickey.his.com/xterm/xterm.faq.html#xterm_terminfo This info is obsoleted. 'bce' issue was already corrected few commits before. -- Andrey A. Chernov http://ache.pp.ru/ msg42327/pgp0.pgp Description: PGP signature
Re: CURRENT's termcap broken
÷ Wed, 28.08.2002, × 23:46, Bruce A. Mah ÎÁÐÉÓÁÌ: If memory serves me right, Jens Schweikhardt wrote: # Do you have time to commit mention of it to UPDATING? If so, please # draw Bruce Mah's attention to the delta so that he can steal your text # for use in the release notes. If not, I'll get around to it eventually. # :-) I just added a note to src/UPDATING. Bruce, are you listening for the release notes? 20020827: Our /etc/termcap now has all the entries from the XFree86 xterm almost unchanged. This means xterm now supports color by default. If you used TERM=xterm-color in the past you now should use TERM=xterm. (xterm-color will lead to benign warnings). After this update, xterm-color produce warnings: vbook:/home/vova 129_ mc TERMCAP, line 0, terminal 'xterm-color': enter_alt_charset_mode but no acs_chars TERMCAP, line 0, terminal 'xterm-color': exit_alt_charset_mode but no acs_chars and midnight commander shows all with -, +, | instead of pesudo-graphics. Ok I have tried setenv TERM xterm, midnight commander now black and white, where I have mistaken ? Bruce. -- Vladimir B. Grebenschikov [EMAIL PROTECTED], SWsoft, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
CURRENT's termcap broken
Hi Jens, I just updated to the latest -current and my TERM=xterm-color applications (mutt and centericq) are broken. Mutt shows this when I start vi as my editor or run fetchmail: TERMCAP, line 0, terminal 'xterm-color': enter_alt_charset_mode but no acs_chars My centericq window ends up using pipe signs (|), minus signs (-) and plus signs (+) to draw boxes. This breakage is visible with the following revisions of the termcap src files: rev 1.129 of src/share/misc/termcap.src rev 1.5 of src/share/misc/reorder Reverting to these revisions of the termcap src files makes things behave as they did before your changes: rev 1.124 of src/share/misc/termcap.src rev 1.4 of src/share/misc/reorder Any ideas? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
Dear all, On Wed, Aug 28, 2002 at 02:48:21PM +0200, Sheldon Hearn wrote: # Hi Jens, # # I just updated to the latest -current and my TERM=xterm-color applications # (mutt and centericq) are broken. # # Mutt shows this when I start vi as my editor or run fetchmail: # # TERMCAP, line 0, terminal 'xterm-color': enter_alt_charset_mode but no acs_chars # # My centericq window ends up using pipe signs (|), minus signs (-) and # plus signs (+) to draw boxes. # # This breakage is visible with the following revisions of the termcap src # files: # # rev 1.129 of src/share/misc/termcap.src # rev 1.5 of src/share/misc/reorder # # Reverting to these revisions of the termcap src files makes things # behave as they did before your changes: # # rev 1.124 of src/share/misc/termcap.src # rev 1.4 of src/share/misc/reorder # # Any ideas? Please use plain TERM=xterm which now has color support. If any problems remain, please let me know. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
Sheldon, On Wed, Aug 28, 2002 at 07:35:32PM +0200, Sheldon Hearn wrote: # On (2002/08/28 19:04), Jens Schweikhardt wrote: # # Yes, use plain TERM=xterm. It's got color now as it should. I'm thinking # of removing xterm-color if I can't resolve the enter_alt_charset_mode # stuff. Let me know if TERM=xterm does not work as expected in mutt et al. # I'll post a minor HEADS UP to current@. # # Doesn't work for centericq or mutt. Are you sure? I use mutt too (in an rxvt), and TERM=xterm works wonderfully with colors. Hang on, will test mutt in plain xterm... yes, works there too. I do have customized my .muttrc and app-defaults/XTerm, however to use different colors from the standard ones. Maybe you have a stale termcap.db? cd /usr/src/share/termcap touch termcap.src make make install should run cap_mkdb termcap and install the termcap.db. # I suspect that a lot of # applications will do explicit testing for [axvt]term-color. This is # naughty, but a fact of life. I wonder why/how these work on systems where the termcaps are also taken from the XFree86 xterm. Could it be something else that's different on your system? I find it hard to believe that any app would scan /etc/termcap and ignoring what it finds in the environment variable TERM. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
In the last episode (Aug 28), Jens Schweikhardt said: On Wed, Aug 28, 2002 at 07:35:32PM +0200, Sheldon Hearn wrote: # On (2002/08/28 19:04), Jens Schweikhardt wrote: # Yes, use plain TERM=xterm. It's got color now as it should. I'm # thinking of removing xterm-color if I can't resolve the # enter_alt_charset_mode stuff. Let me know if TERM=xterm does not # work as expected in mutt et al. I'll post a minor HEADS UP to # current@. # # Doesn't work for centericq or mutt. Are you sure? I use mutt too (in an rxvt), and TERM=xterm works wonderfully with colors. Hang on, will test mutt in plain xterm... yes, works there too. Older versions of the mutt port used the slang terminal library, which had (has?) a bug that assumed that all xterms supported color. It didn't matter what your termcap says. If tput Co prints '8', your termcap entry supports colors. If ldd usr/local/bin/mutt shows libslang instead of libncurses, it'll display colors no matter what. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
On (2002/08/28 20:32), Jens Schweikhardt wrote: # Yes, use plain TERM=xterm. It's got color now as it should. I'm # thinking of removing xterm-color if I can't resolve the # enter_alt_charset_mode stuff. Let me know if TERM=xterm does not # work as expected in mutt et al. I'll post a minor HEADS UP to # current@. # # Doesn't work for centericq or mutt. Are you sure? I use mutt too (in an rxvt), and TERM=xterm works wonderfully with colors. Hang on, will test mutt in plain xterm... yes, works there too. I do have customized my .muttrc and app-defaults/XTerm, however to use different colors from the standard ones. Maybe you have a stale termcap.db? Argh, how stupid of me. I tried removing TERM=xterm-color without rolling forward to your latest version where xterm has colour support! Your fix works great, thanks. Do you have time to commit mention of it to UPDATING? If so, please draw Bruce Mah's attention to the delta so that he can steal your text for use in the release notes. If not, I'll get around to it eventually. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
Sheldon, # Maybe you have a stale termcap.db? # # Argh, how stupid of me. GUMPStupid is who does stupid things/GUMP :-) # I tried removing TERM=xterm-color without rolling forward to your latest # version where xterm has colour support! # # Your fix works great, thanks. # # Do you have time to commit mention of it to UPDATING? If so, please # draw Bruce Mah's attention to the delta so that he can steal your text # for use in the release notes. If not, I'll get around to it eventually. # :-) I just added a note to src/UPDATING. Bruce, are you listening for the release notes? 20020827: Our /etc/termcap now has all the entries from the XFree86 xterm almost unchanged. This means xterm now supports color by default. If you used TERM=xterm-color in the past you now should use TERM=xterm. (xterm-color will lead to benign warnings). Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT's termcap broken
If memory serves me right, Jens Schweikhardt wrote: # Do you have time to commit mention of it to UPDATING? If so, please # draw Bruce Mah's attention to the delta so that he can steal your text # for use in the release notes. If not, I'll get around to it eventually. # :-) I just added a note to src/UPDATING. Bruce, are you listening for the release notes? 20020827: Our /etc/termcap now has all the entries from the XFree86 xterm almost unchanged. This means xterm now supports color by default. If you used TERM=xterm-color in the past you now should use TERM=xterm. (xterm-color will lead to benign warnings). I'm on it, thanks for the heads-up. Are you thinking of merging this for 4.7? Bruce. msg42272/pgp0.pgp Description: PGP signature
