[46] in bug-owl
weird artifacts
daemon@ATHENA.MIT.EDU (Jeremy Daniel)
Sun Jun 30 01:10:18 2002
To: bug-owl@MIT.EDU
From: Jeremy Daniel <jdaniel@MIT.EDU>
Date: 30 Jun 2002 01:10:15 -0400
Message-ID: <skeofdt8i88.fsf@multics.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
The main problem here involves characters in the message which take up
more than one column the way you're printing them. In particular the
following examples contain the characters '^_' and '^A'. Here are the
symptoms I am seeing.
-D H. J. Lu -DISCUSS ^_GCC 88777: Re: optimization/7145: g++ -
O jsmthng -jsmthng
The particular problem here is the 'O' in the left column of the
second line. It's actually the next character from the previous line,
printing when it should not. Owl's counter of what to print is thrown
off one by the '^_'.
-D H. J. Lu -DISCUSS ^_GCC 88777: Re: optimization/7145: g++ -
D foobar -foobar
Once I delete the message it appears normal, but if I undelete it it
returns how it was. I think the " D" is overwriting the character.
If I change the screen width it continues to be always the next
character off the screen which will appear in the first column.
Here's an example of making it very narrow and how many lines such an
artifact can throw off. Notice how it doesn't fix itself until you
get to the first visible '\n' on the page.
-D H. J. Lu -DISCUSS ^_GCC
8 foobar -foobar
yikes, larger-than-I-want credit c
a but I guess more than half of it i
D bazquux
{ bazquux
( not yet. tomorrow
-> daemon -sipb-auto .sipbmp3 (
Playback completed successfully.
No ID3 tag found
Filename: g/Gin Blossoms/Gin Blossoms
----------------
Here's a very different but also weird example:
olc.matiss -olc .new_question {test} (From: OLC Service~New "test" question from user mitchb [0].~^A^A^A^A^A^A^A^
DA^A^A^A^A^A^A OWL ADMIN Message sent to foobar bazqux
This particular one only happens at rather wide screen widths or when
scrolled to the right. I think the problem here is that $owl::body
never got initialized to '\0'. So when my default format function
appended it something weird must have happened. I counted and there
appear to be 160 or so '^A' characters in the body of this message.
-----------
I hope you find these descriptions useful enough to debug. For
reference I am using $TERM=screen on a screen from gnu inside PuTTY,
but I'm thinking that shouldn't make such a difference, especially for
the failure to initialize $body one.
--
Jer
------------------------------------------------------------------
Tulgey Wood - tulgeywood@attbi.com Cell Phone: 617-429-8573 /
4 Farragut Ave (617-629-3983) jdaniel-phone@mit.edu
Somerville, MA 02144-1709 AIM: jdanielmit
Zephyr athena users over the web: http://webzephyr.mit.edu/
