Please keep the bug address in the Cc list, it logs the history of the
problem and discussions about it for future reference (including by me as
I sit down and try to figure out if the problem's fixed..)
On Thu, Aug 30, 2001 at 07:05:54PM +0200, Kurt Roeckx wrote:
> > Using epic4 with thirdeye and xterm.
> >
> > Topics up to and including 232 characters in length are handled
> > correctly. Character 233 causes the terminal bell to ring. Any
> > characters at position 234 or greater corrupt the display and are
> > written into the status line and/or command line.
>
> I just recompiled my ircd to support 300 char topics set one of
> 300 chars, and nothing special happened, it all works as
> expected.
Now that figures, naturally. I've also never noticed a problem, but I
also had not been looking for it.
> Tested with:
>
> *** Client: ircII EPIC4-1.0.1 (Internal Version: 20010730)
> and:
> *** Client: ircII EPIC4-1.0 (Internal Version: 20010401)
>
> Is thirdeye a script? Where can I get it to test it?
It is - http://knuckle.sandwich.net/te/
I'm having trouble connecting to this right now. Here's a link to the
version used by Branden:
ftp://ftp.debian.org/debian/dists/woody/main/source/net/epic4-script-thirdeye_1.72.orig.tar.gz
There is a diff alongside it which applies trivial changes to integrate it
with my default script mechanism and wraps the script for global
installation, but those things should not have any effect on the script in
this capacity.
Perhaps the problem is related to ncurses and xterm? Given the complexity
of either, it would not come as a surprise to me. I am guessing the magic
232 character limit is probably based on how TE formats the topic first,
and second the widto of the terminal used. I'm not seeing it with my
modified version of lice.
--
Joseph Carter <[EMAIL PROTECTED]> Free software developer
* Knghtbrd notes he has mashed potatoes for brains tonight
<Valkyrie> yum, can I have some?
<Knghtbrd> um ...
* Knghtbrd hides from Valkyrie
PGP signature
