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
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 en
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)
÷ 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 o
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 s
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 (
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
>
...
# > # 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.fa
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'
> > 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
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
> 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_ cor
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 o
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 attenti
÷ 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
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
Sheldon,
# > Maybe you have a stale termcap.db?
#
# Argh, how stupid of me.
Stupid is who does stupid things :-)
# 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 comm
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 po
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
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 kno
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, termin
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 usi
22 matches
Mail list logo
